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.
git clone --depth 1 https://github.com/DSB-117/brainblastWrote 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/commands/dsb-117/brainblast/brainblast-rico-maps)<a href="https://agentmods.dev/commands/dsb-117/brainblast/brainblast-rico-maps"><img src="https://agentmods.dev/badge/commands/dsb-117/brainblast/brainblast-rico-maps.svg" alt="Measured on agentmods" 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.00000 | $0.00374 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
brainblast-rico-maps 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 8d 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.
What it actually says
/brainblast-rico-maps
Runs a two-part token check on any Solana contract address (CA):
-
Identity — verifies the token against Jupiter's canonical registry and a bundled snapshot of blue-chip mints (USDC, USDT, SOL, JUP, etc.). Flags impersonators claiming canonical symbols at wrong addresses.
-
Quality — calls Rico Maps
/api/v1/analyzefor forensic risk scoring: holder concentration, cabal detection, snipers, bundle clusters, deployer flags.
Usage
/brainblast-rico-maps <contract-address> [--expect SYMBOL] [--api-key KEY] [--fail-on SCORE] [--offline]
--expect SYMBOL— assert the token should be this symbol; fails if wrong--api-key KEY— Rico Maps API key (prompted interactively if absent)--fail-on SCORE— exit 1 if risk score ≥ this value (default: 70)--offline— skip network calls; identity check uses bundled snapshot only
What it does
npx brainblast rico $ARGUMENTS
Exit codes:
0— identity ok, risk score below threshold1— impersonation detected, expect mismatch, or risk score ≥ threshold
API key
Rico Maps offers an anonymous free tier (10 req/min, 1000/month). If no key is provided, the command attempts an anonymous request. If the server rejects it, you'll be prompted:
No Rico Maps API key found. Options:
[s]kip — skip the quality scan, identity check only
[k]ey — enter your API key (ricomaps.fun/dashboard)
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.
- 8d ago First seen · 39 lines · 0 tokens per session scan A 416e51cebd50
brainblast-rico-maps is a command published in the GitHub repository DSB-117/brainblast (100 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 374 tokens. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.