Borrowing it
Nothing to install: this file belongs to DSB-117/brainblast. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DSB-117/brainblast/main/.claude/skills/brainblast-fleet/SKILL.mdgit 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/skills/dsb-117/brainblast/brainblast-fleet)<a href="https://agentmods.dev/skills/dsb-117/brainblast/brainblast-fleet"><img src="https://agentmods.dev/badge/skills/dsb-117/brainblast/brainblast-fleet.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.00079 | $0.01880 |
| Opus 5 | $0.00039 | $0.00940 |
| Sonnet 5 | $0.00016 | $0.00376 |
| Haiku 4.5 | $0.00008 | $0.00188 |
Grade A, and why
brainblast-fleet scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "${FLEET_REGISTRY_URL:-https://registry.brainblast.tech}/api/vti" | jq '.count, [.records[].id]' How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainblast Fleet
The autonomous successor to hand-dropping candidates. You (the orchestrating agent) run this skill; it fans out a fleet of subagents — one per repository — to do the scouting, then the deterministic engine proves, promotes, submits, and logs. The model doing the reasoning is whatever agent is running Brainblast (this one) — no API key is requested.
The non-negotiable invariant: only traps that prove RED→GREEN through the
existing checkers ever land. Subagents propose; proveFinding disposes.
Run from packages/core/. Five phases.
Phase 0 — Pick targets
If the user named SDKs/protocols, use them. Otherwise read the work-orders the
last run left — cat ../../fleet/REPORT.md or datasets/COVERAGE.md — and target
the uncovered classes and thin cells, freshness-first (recently-shipped
or high-download SDKs, where models are most stale).
Phase 1 — Discover (deterministic)
For each target SDK:
npm run fleet:discover -- --sdk <pkg> --limit 10 --min-stars 200
Writes fleet/worklist.json (popular dependent repos, ranked by stars, already
filtered against the shared ledger so you don't re-scout what another fleet did).
Read it. If it's empty, the ledger says everything popular here is already done —
pick another SDK.
Phase 2 — Scout (fan out the subagent fleet)
For each repo in the worklist, spawn a subagent (the Agent tool,
general-purpose). Launch them in parallel batches (e.g. 3–5 at a time). Give
each subagent EXACTLY this contract:
Scout
<owner/repo>for a silent integration footgun in its use of<sdk>: code where the happy path compiles and runs but does the wrong thing (an insecure-default flag, a zeroed fee/amount, a skipped verification, a wrong constant). Shallow-clone read-only (git clone --depth 1) into a temp dir. For each real footgun you find that fits an existing brainblast checker (object-arg-property-forbidden-literalis the workhorse — an options-object property set to a forbidden string/number/boolean literal), write a candidate Finding tofleet/candidates/<id>.jsonfollowingfleet/README.md. Thevulnerablefixture must contain the forbidden value; thefixedfixture must set a safe literal (so it PASSES). Setclass. Capture provenance from the real code — the registry requires it: record the exactgit rev-parse HEADof the shallow clone and, in the candidate'sprovenance, setsourceReftogithub.com/<owner>/<repo>/blob/<that-sha>/<path>andevidenceto the verbatim vulnerable line as it appears in the file. Without a real, fetchable sourceRef + evidence the finding can only enter the repo seed corpus, never the registry. Do not fabricate — if the repo has no provable footgun, write nothing and report "clean". Return: repo, the candidate ids you wrote (or "clean"), and a one-line note per finding.
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.
- 7d ago First seen · 165 lines · 79 tokens per session scan A 71fd71a54d6c
brainblast-fleet is a skill published in the GitHub repository DSB-117/brainblast (100 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 1,880 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
Flaky Test Doctor
Diagnose flaky test failures from Playwright reports, traces, and rerun history. Classify each failure as product, test, environment, data, or unknown with cited evidence and a proposed fix. Never auto-modifies code without opt-in.
debug-loop
Use when diagnosing failing tests, stack traces, and repeated errors with a hypothesis-driven debug loop.
red-green-testing
Use when writing failing tests first, running red-green cycles, and keeping regression tests focused.
mk:lint-and-validate
Automatic quality control, linting, and static analysis after code modifications. Triggers on: lint, format, check, validate, types, static analysis. NOT for full build verification (see mk:verify); NOT for test coverage (see mk:testing).
test-and-fix
A test-repair tool that runs tests, analyses failures, and repeatedly applies automated fixes.
lint-and-validate
Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.