Agent 001 · CoinMarketCat · the console

The sniper cat's console

CoinMarketCat crouches ten seconds over every new launch and pounces only if it is still at or above its entry price. This page is where it meets your wallet: the extension runs the cat, Phantom lives here, and every approval the cat asks of Phantom comes from this tab. Keep this tab open while the cat is armed. (On Autopilot, the cat's own wallet signs its trades, and this tab is needed only to fund that wallet from Phantom.)

looking for the extension…
—
Wallet
—
Feed
—
Today
—
Live book
—
Shadow book
—
Rule
—

No extension yet? It is not in a store. You build it from the repository and load it unpacked — the steps are below and on CoinMarketCat's page. Until then this page is a description, and the panel above stays quiet.

What the cat does, and what it does not

It listens to pump.fun's own program logs, runs every launch through the same entry contract WALL-ST-E runs — the executor's snipe-entry.mjs, vendored from a named commit of Claude-Company and hashed — and keeps a would-have position for every launch that clears, sampled forward into a shadow book in the executor's own row schema. That book grades the two entry rulers the rug literature names, and you can export it and grade it with the command the repository ships.

When you arm it, a cleared launch becomes a buy only after it is ten seconds old and still marks at or above its own would-have fill — then the lane re-reads the curve, rebuilds and simulates the exact buy_v2 it will sign, and asks Phantom. The position leaves in full at the take, the stop, the creator's exit or the clock, and in Phantom mode each of those is one more Phantom window. A stop that needs a click is a weaker stop than a key's. A sell you decline is asked again eight seconds later, and a window you leave unanswered is abandoned after thirty-two seconds and asked again, for as long as the determiner still says sell; it cannot answer for you.

In Phantom mode — the default — it never sees a key. On Autopilot it holds exactly one: the key of the separate wallet it created, encrypted under your passphrase, in your browser only (the trade-off, plainly). Either way it does not use Phantom's sign-and-send; it sends the bytes you signed through the RPC you chose, with preflight skipped, exactly as the executor does, and it refuses to send anything whose message is not the one it asked you to sign.

What the desk's losing record taught it

The executor's live record, read back off mainnet in full on 2026-09-17: 10 up, 48 down, −1.58 SOL over 58 round trips; six more under the socials filter and the stall exit went 1 up, 5 down. Eighteen positions ran to the old ten-minute clock and none won. Every SOL of the net loss sat in tickets of 0.35 SOL and up.

seconds late at entrynwonmean realised
under 3s90%−18.5%
3–6s2520%−2.6%
6–10s2010%−23.4%
10s and later1040%+34.0%

The fastest entries were the worst. The plausible mechanism is the one the rug literature describes: a launch reachable inside three seconds is one already bundled, and arriving right behind the bundle makes you its exit liquidity. So this lane waits, and buys only what somebody else followed. It takes at 1.5× rather than 2×: 44% of the coins reached 1.5× and the bot realised it on five of them; 25% reached 2×. It keeps the stall exit at 90 seconds and the time stop at three minutes, because the ten-minute bucket was 18 for 18.

None of this is evidence of an edge. Nothing measured at entry ordered the outcome (every Spearman ρ under 0.13 at n=64), and every modelled exit ladder over the 64 still loses. What the record supports is a rule that keeps this lane out of the one bucket that never won, and a shadow book that will say, over thousands of unselected rows, whether the rulers separate anything. Observe first. Grade the book. Arm a canary.

Install

  1. Clone the repository and build the extension:
    git clone https://github.com/gtjvv976mb-netizen/Cat-Intelligence-Agency
    cd Cat-Intelligence-Agency && npm ci && npm run build
  2. Open chrome://extensions, turn on Developer mode, press Load unpacked, choose Cat-Intelligence-Agency/dist.
  3. The setup page opens on install: paste an RPC URL — Helius, Triton or QuickNode; the public RPC refuses browsers — set your limits and choose who signs. Saving puts the cat in Observe.
  4. Come back to this page, press Connect Phantom, approve the connection.
  5. Leave it on Observe. Watch the shadow book fill. Export it and grade it with node vendor/executor/grade-entry-gates.mjs --file <export>.
  6. Only then: Execute, at the 0.005 SOL canary, with the sentence the lane prints for your wallet typed into the box.

What this is. CoinMarketCat is Agent 001 of Cat Intelligence Agency. A user-operated tool that runs in your own browser against your own wallet. No server receives a key, signs, or can reach this lane; this page ships no signing code — the extension you built carries it. Not advice, not a signal service, and nothing here has an edge until you have graded its book over a real sample. In Phantom mode every position it opens can be sold only by a click you make; if you close this tab, the lane cannot ask. On Autopilot a locked wallet signs nothing, sells included.

Cat Intelligence Agency is a meme and software project. It is not affiliated with any government agency, CoinMarketCap, or the owners of any real cat.
$CIA is a memecoin with no intrinsic value. Nothing here is financial advice.