SkillAgentSearch skills...

themonitor

Monitor, autonomous trading intelligence on Elysium (Kinetiq's chain, id 99901), app at app.themonitor.bot. It watches every block, waits for confluence among the strongest on-chain wallets and trades from the user's own smart account

Install / Use

npx skills add BankrBot/skills --skill themonitor

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

91/100

Category

Operations

Supported Platforms

Universal

Tags

Our assessment of themonitor

themonitor scores 91/100 on our quality scale, 274th of 763 Operations skills we index (top 36%).

Its SKILL.md is 19 KB long, well organised into 17 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.

With 1,201 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so themonitor is actively maintained.
  • Our last check on 2026-11-19 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-11-19. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

themonitor compared with similar skills

All 4 of these similar skills score higher than themonitor; compare them before choosing.

SkillScoreStarsUpdatedFormat
themonitor (this skill)by BankrBot911.2k57d agoSKILL.md
algorithmic-artby anthropics100177.9k58d agoSKILL.md
pptxby anthropics100177.9k58d agoSKILL.md
prospectingby coreyhaines3110060.1k8d agoSKILL.md
ad-creativeby coreyhaines3110060.1k8d agoSKILL.md

Frequently asked questions

How do I install themonitor?
Run npx skills add BankrBot/skills --skill themonitor. The install tabs above show the steps for each supported agent.
Which AI agents does themonitor work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is themonitor safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is themonitor still maintained?
The repository was last updated about 2 months ago, so themonitor is actively maintained.

name: themonitor description: Monitor, autonomous trading intelligence on Elysium (Kinetiq's chain, id 99901), app at app.themonitor.bot. It watches every block, waits for confluence among the strongest on-chain wallets and trades from the user's own smart account. Use when the user wants Monitor to trade part of their HYPE on Elysium, check the status or P&L of that account, sell a position, add funds, stop and withdraw everything, or revoke its permissions. The funds sit in the user's own smart account; the Bankr wallet signs scoped, time-limited permissions and sends one deposit transfer. tags: [trading, autonomous-trading, smart-money, elysium, hype, defi] version: 1 metadata: clawdbot: homepage: "https://app.themonitor.bot/app/" requires: bins: [curl, jq] packages: [viem@2.57.16]

Monitor on Elysium

Monitor (https://themonitor.bot, app at https://app.themonitor.bot/app/) is an autonomous trading agent on the Elysium chain (id 99901, gas coin HYPE). It watches every block, tracks the strongest on-chain wallets, waits for confluence and trades from the user's own smart account, with a per-trade size the user picks. The fee is 15% (Balanced) or 20% (Aggressive) of profit above the account's high-water mark, taken when money is withdrawn. No performance is promised: these are new, unvalidated wallets on a young chain, and meme-coin trading can lose most of the money put in.

What the user is agreeing to

  • Non-custodial. Funds are held by a smart account that the user's wallet owns. Monitor cannot move them except within the permissions below.
  • Four permissions, each an EIP-712 signature by the user's wallet (about one year, then they must be renewed):
    1. swap: Elysium's server key may call only buy and sell on one guarded swap contract (0x795f8ff1d458a168b78e3c37c028fb834d1146d5), up to a per-call value cap and a 24-hour cap, and a fixed number of calls. The contract pays swap output only to the user's account.
    2. approve: the same key may approve token spending, with the spender fixed to that contract.
    3. withdraw: the key may send native HYPE out of the account only to the user's own wallet address.
    4. feegas: the key may pay the performance fee and a gas refund, only to the fee address (0x509c3978687c9fb3e94a11b84703796f75f51588), up to a cap.
  • The user can stop at any time (agents stop, positions are sold, cash is withdrawn to the Bankr wallet), and can revoke the permissions on chain from their own wallet (Step 9). Withdrawals are sent by the Elysium server; if it is unreachable, say so and tell the user to retry later.
  • The agent must never ask the user to sign or send anything other than what is described in this file.

Requirements on the Bankr side

  1. A Bankr API key with Wallet API enabled and read-only off.
  2. Arbitrary contract calls must be switched on (Bankr security settings, needs MFA). Without it /wallet/sign refuses typed data (error MFA_REQUIRED or 403). Suggest the 10-minute to 24-hour timer so it switches itself off afterwards. Permitted recipients must be off while signing, otherwise typed data is refused too.
  3. HYPE in the Bankr wallet on Elysium (not HyperEVM). Bankr can bridge HYPE HyperEVM -> Elysium in chat. The deposit amount plus about 0.01 HYPE for gas must be there. Gas is paid by the wallet and is never sponsored.
  4. Name the chain every time: "Elysium", chain id 99901. Never default to HyperEVM (chain 999).

Constants

| Item | Value | |---|---| | API base | https://app.themonitor.bot/api | | Chain id | 99901 (RPC https://rpc.agoradex.app, https://rpc-live.elysp.com) | | Delegation manager (typed-data verifyingContract) | 0xdb9B1e94B5b69Df7e401DDbedE43491141047dB3 | | Executor (typed-data delegate) | value of executor in /live/state (production: 0x7Fea74C5eB9acaeFd7fC2f9c627b5d286E134940) | | Guarded swap contract | 0x795f8ff1d458a168b78e3c37c028fb834d1146d5 | | Fee address | 0x509c3978687c9fb3e94a11b84703796f75f51588 | | Per-buy size limits | 0.0145 HYPE (about $1) to 145 HYPE |

Every request is POST with Content-Type: application/json unless marked GET. Send the header X-Elysium-Client: bankr on every call. After sign-in also send Authorization: Bearer <token>. Keep the token in memory for the conversation only and never print it. All amounts in the API are HYPE (fields are named *_eth), decimal strings or numbers.

If any call answers 403 Request not allowed from this page., the agent access is not enabled on the server yet: tell the user and stop.

Step 0. Look around (public, no sign-in)

  • GET /api/status -> {chain: 99901, traders}.
  • GET /api/ethusd -> {usd} is the HYPE price in USD. If it has stale: true and age over 300, do not move money.
  • GET https://app.themonitor.bot/app/strategies.json -> strategies[] with id (elite = Aggressive, 20% fee, 7% of the account per buy; wave = Balanced, 15% fee, 5% per buy), leaders[] (ids like E4), ticket_pct, take_x, status, bt. Read status and bt and tell the user what they say (at the time of writing: dry-run, no backtest, forward validation required).
  • GET /api/leaders -> map of leader id to {short, verdict, note}. Drop any leader whose verdict is reject.
  • GET /api/balance/{address} -> {eth} native HYPE balance of any address on Elysium.

Step 1. Plan with the user (nothing signed yet)

Ask for: strategy (wave or elite), amount to put in (HYPE or USD), and confirm the per-buy size. Default per-buy = ticket_pct% of the amount, clamped to 0.0145..145 HYPE. Show: amount, per-buy size, fee percent, the four permissions above, that the first signature creates the account record, and the risk sentence. Ask for an explicit "yes". Tell the user that the signed per-buy ceiling (about 1.3x the per-buy size) will be shown before signing; a larger per-buy size later needs one new swap signature. The amount and per-buy size set the caps inside the permissions, so decide them now: caps = {"amount_eth": <amount>, "ticket_eth": <per-buy>}.

Step 2. Sign in and sign the first permission

Let ME = the Bankr wallet's EVM address (lowercase). It must hold the HYPE on Elysium.

New wallet (the first permission is also the sign-in):

  1. POST /api/live/prepare body {"kind":"swap","address":ME,"mode":"sa","opt":caps} -> {kind, typedData}.
    • 401 Connect your wallet first. means this wallet already has an account: go to "Returning wallet" below.
    • 403 The live beta is full right now.: tell the user, stop.
  2. Run the checks in "Checking a permission" on typedData (the delegator is not yet comparable to a server-reported account, so compute it with scripts/verify-account.mjs ME and require delegator = that address).
  3. Show the user what is being signed (kind swap, the exact limits printed by the check, expiry) and ask for confirmation of those numbers.
  4. Sign with the Bankr wallet: POST https://api.bankr.bot/wallet/sign (header X-API-Key) body {"signatureType":"eth_signTypedData_v4","typedData": <typedData with types.EIP712Domain removed>} -> {signature}. (CLI: bankr wallet sign --type eth_signTypedData_v4 ....)
  5. POST /api/live/submit body {"kind":"swap","address":ME,"signature":SIG} -> {ok:true, kind, token}. Keep token.

Returning wallet (account exists, no token):

  1. POST /api/auth/nonce {"address":ME} -> {nonce, message}.
  2. Sign message exactly as given (including line breaks) with signatureType: "personal_sign", message: <message>. This message moves nothing.
  3. POST /api/auth/verify {"address":ME,"nonce":NONCE,"signature":SIG} -> {address, token}.

Step 3. Create the account and sign the rest

  1. POST /api/live/state {} -> note account (the smart account address), deployed, executor, to_sign, mode (must be "sa"), swap_cap_eth.
  2. Run node scripts/verify-account.mjs ME and require the printed address to equal account. If not, stop and tell the user: nothing may be sent to that address.
  3. If deployed is false: POST /api/live/deploy {} -> {ok:true} (Elysium's server pays for deployment). Then state again.
  4. For each kind in to_sign (for a fresh account: approve, withdraw, feegas; swap is already done):
    • POST /api/live/prepare {"kind":kind,"opt":caps} -> {typedData}.
    • Run the check, show the user the printed limits, get confirmation (you may group the remaining ones in one confirmation, but list each with its limits).
    • Sign as in Step 2, then POST /api/live/submit {"kind":kind,"signature":SIG} -> {ok:true}.
  5. state again. to_sign must be empty. Do not sign exit or exit_approve (optional cold-key permissions; skip them).

Checking a permission before the wallet signs it

Save the typedData from prepare to a file and run:

node scripts/check-permission.mjs KIND typedData.json ME ACCOUNT AMOUNT PER_BUY

(ACCOUNT = account from state, or the address computed in Step 2; AMOUNT and PER_BUY = the amount and per-buy size the user agreed in Step 1.) If it prints STOP: ..., do not sign: tell the user the reason and stop. The script refuses unless all of this holds:

  • domain is DelegationManager v1, chainId 99901, verifyingContract = the delegation manager above; primaryType is Delegation; delegator = ACCOUNT; delegate = Monitor's executor key; authority = root (0xff..ff).
  • The caveats are exactly the expected set for the kind, each identified by its pinned enforcer address on Elysium (nothing missing, nothing extra, no duplicates, no args), and each terms matches Monitor's encoding byte for byte:
    • swap: AllowedTargets = exactly the guarded swap contract; AllowedMethods = exactly buy and sell (0xf496a610, 0x3581f5bb); ValueLte (per-buy cap); NativeTokenPeriodTransfer with a 24-hour period; LimitedCalls; Timestamp.
    • approve: AllowedMethods = exactly 0x095ea7b3; AllowedCalldata = exactly 64 bytes, offset 4 followed by the guarded swap contract padded to 32 bytes (so the bound argument is the spender, not the amount); ValueLte = 0; Timestamp.
    • withdraw: ExactCalldata empty (plain transfers only); AllowedTargets = exactly ME; NativeTokenTransferAmount; Timestamp.
    • feegas: same as withdraw, but AllowedTargets = exactly the fee address.
    • Timestamp: valid from now until a date at most 400 days away.
  • For swap, the signed per-buy cap is between 1x and 1.5x the agreed per-buy size (Monitor signs 1.3x: room for the size jitter of up to 15%). A cap outside that range is refused, so a single buy can never spend the whole deposit.

On success the script prints the decoded limits. Show these exact numbers to the user and get an explicit "yes" for them before signing, in particular for swap:

  • max_per_buy_hype: the most a single buy can spend (about 1.3x the per-buy size), e.g. "one buy can spend at most 0.13 HYPE; your size per buy is 0.1 HYPE".
  • max_per_24h_hype and max_calls: the 24-hour spending ceiling and the total number of swap calls.
  • For feegas, max_total_hype is the most that can ever be paid to the fee address; for withdraw, money can only go to the user's own wallet.

If the user does not accept a ceiling, do not sign. Run the same check every time a permission is renewed or replaced (Step 5, Step 7). Only these kinds are ever requested: swap, approve, withdraw, feegas. The only other typed data the agent ever signs is the revoke PackedUserOperation in Step 9, after the checks listed there.

Step 4. Deposit

Only after Step 3 is clean and the user confirms the exact amount and the destination account:

  • Send the amount as native HYPE on Elysium (chain id 99901) from the Bankr wallet to account. Either use Bankr's normal transfer ("send X HYPE on Elysium to ACCOUNT"), or the raw call: `POST https://api.bankr.bot/wallet/submi

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryOperations
Updated1mo ago
Forks629

Languages

JavaScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium