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 agentmods add commands/dsb-117/brainblast/brainblast-packsgit 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-packs)<a href="https://agentmods.dev/commands/dsb-117/brainblast/brainblast-packs"><img src="https://agentmods.dev/badge/commands/dsb-117/brainblast/brainblast-packs.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.00316 |
| Opus 5 | $0.00000 | $0.00158 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
brainblast-packs 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 6d 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-packs
The Protocol Pack Library. Every Solana app is built on some combination of Jupiter, Raydium, Pyth, Meteora, Jito, … — each with its own silent footguns. Opt into research-and-enforcement for the exact stack you build on.
Usage
List the bundled packs by protocol name:
npx brainblast packs
Then audit with the packs for your stack (each is opt-in, not loaded by default):
npx brainblast --packs jupiter,pyth .
--packs <name> resolves a protocol name (e.g. pyth) to its bundled pack, or takes an explicit pack directory. Packs are pure data (rules bind only to vetted checker templates) and every rule ships vulnerable/+fixed/ fixtures proven RED → GREEN.
Bundled protocols
jupiter (zero-slippage quote) · raydium (zero-slippage swap) · pyth (unchecked price staleness) · meteora (zero min-out) · jito (zero bundle tip) · metaplex (zero royalties) · solana (sendTransaction unconfirmed) · spl (unchecked transfer).
Validate or author a pack:
npx brainblast pack validate <dir>
npx brainblast pack init packs/<id> --id <id> --name "<name>" --author <you>
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.
- 6d ago First seen · 31 lines · 0 tokens per session scan A 4816740f82ab
brainblast-packs 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 316 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.