Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add solsentry/solsentry-mcp --skill solsentry-postdeploygit clone --depth 1 https://github.com/solsentry/solsentry-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/solsentry/solsentry-mcp/solsentry-postdeploy)<a href="https://agentmods.dev/skills/solsentry/solsentry-mcp/solsentry-postdeploy"><img src="https://agentmods.dev/badge/skills/solsentry/solsentry-mcp/solsentry-postdeploy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/solsentry/solsentry-mcp/solsentry-postdeploy"><img src="https://agentmods.dev/badge/skills/solsentry/solsentry-mcp/solsentry-postdeploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00066 | $0.01126 |
| Opus 5.5 | $0.00026 | $0.00450 |
| Sonnet 5.5 | $0.00013 | $0.00225 |
| Haiku 4.5 | $0.00007 | $0.00113 |
Grade A, and why
solsentry-postdeploy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 26d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SolSentry tracks the operators behind Solana token launches and program deployments — serial rug pull operators, coordinated bot clusters, and malicious wallets. This skill exposes that intelligence to AI agents at the post-deploy stage of a Solana developer workflow.
The skill complements pre-deploy security tooling (auditing, formal verification, secure code generation) by answering the questions that only become relevant after code ships:
- "Is the wallet about to interact with my program a known rugger?"
- "Did the deployer of this program have a prior rug history?"
- "Where did the SOL drained from my LP go?"
- "Is the operator I'm about to integrate with via CPI clean?"
This skill is bilingual-aware (the underlying alerts and explainer support
PT-BR and EN), and all data is sourced from the public REST API at
api.solsentry.app — no API key required for read endpoints.
When to load each reference
Load only the reference relevant to the user's current task. Do not load all references at once — they are progressive disclosure files.
| Reference | Load when |
|---|---|
references/threat-intel.md |
User asks for risk on any wallet or mint — generic lookup, no specific workflow |
references/counterparty.md |
User is integrating with another program (CPI), oracle, or deployer they did not write themselves |
references/monitor.md |
User shipped a program or token and wants ongoing visibility on activity touching it |
references/forensics.md |
User reports an incident — drain, exploit, suspicious flow — and needs post-mortem trace |
references/token-launch.md |
User is preparing to launch their own token and wants to know if it will be flagged or bundled |
references/cluster-graph.md |
User is researching the operator/bot network around a wallet, mint, or scam pattern |
Tools (MCP)
The @solsentry/mcp server exposes exactly these 4 tools. Everything else
in the references (alerts, resolutions, clusters, operator timeline,
drain-trace) is reached through the public REST API directly, not through an
MCP tool.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 26d ago Changed · +20 lines b9d77e4500e1
- 1mo ago First seen · 89 lines · 66 tokens per session scan A 1897dc1a82db
solsentry-postdeploy is a skill published in the GitHub repository solsentry/solsentry-mcp (2 stars, last pushed 17d ago), licensed MIT. It adds 66 tokens to every session and 1,126 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
okx-cex-earn
A tool for managing several earning products on OKX, including savings, lending, staking, DeFi, Dual Investment, and AutoEarn. These products can use deposited cryptocurrency to generate returns, with terms that vary by product.
rustchain-mcp
This skill allows Claude Code to interact with the RustChain blockchain, monitor the network, and hunt for bounties.
hive
Use this skill for any live crypto question and for Hive setup, on MCP or the hive CLI. Covers current market, on-chain, wallet, token-safety, DeFi, NFT, Solana, prediction-market, and derivatives data, plus the questions other crypto data tools cannot answer, meaning perp funding settlement history across 33 venues…
hive-market-research
Use this skill for any live crypto market question — prices, 24h moves, liquidity, exchange/venue data, OHLC candles, order books, tickers, funding rates, derivatives, trading context — even casual asks like "what's BTC at" or "is ETH pumping". Use it whenever the answer needs current market numbers instead of memory.…
hive-query
Use this skill when the hive skill hands off a live crypto question that needs the full task-toolset walk (prices, wallets, tokens, DeFi, NFTs, Solana, security, markets, DEX, networks, RWA perps, prediction markets) and no hero tool answers it in one call. Install hive first; reach for this directly only when the…
hive-security-risk
Use this skill before the user signs, approves, swaps, connects a wallet to a dApp, or touches an unknown contract, URL, or transaction payload — any "should I sign/approve/ape/connect" moment, even when the user only implies the transaction. Runs token, address, approval, phishing, and simulation risk checks and…