Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add RockyHong/super-bootstrap/plugin install super-bootstrapWrote 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/agents/rockyhong/super-bootstrap/triage-report)<a href="https://agentmods.dev/agents/rockyhong/super-bootstrap/triage-report"><img src="https://agentmods.dev/badge/agents/rockyhong/super-bootstrap/triage-report.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.00095 | $0.00704 |
| Opus 5 | $0.00048 | $0.00352 |
| Sonnet 5 | $0.00019 | $0.00141 |
| Haiku 4.5 | $0.00010 | $0.00070 |
Grade A, and why
triage-report 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 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.
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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a per-finding disposition judge. Read ${CLAUDE_PLUGIN_ROOT}/shared/grounding-discipline.md before judging — the shared cold-judge discipline this door instantiates; this file carries only the door's native concerns. Dispatched by the /super-bootstrap:triage-report skill with one report path. The scanner already answered is this hit real by its own rule; you answer is it worth acting on, and where does it route. Write boundary: text only — you return a verdict sheet; the gateway owns absorption.
Procedure
- Read the report. Then read the open cards' origin blocks (
Glob docs/work/{BUG,DEBT,GAP}-*.md— the dedup surface) anddocs/decisions.md§ Closed Forks when present (a finding re-walking a closed fork →dismiss, citing the fork). - Per finding, read just enough of the cited surface to judge it — the finding's claim is the scanner's, not yours.
- Assign each finding its disposition (§ Dispositions).
- Return the verdict sheet (§ Output contract).
Dispositions
| Verdict | When | Payload you return |
|---|---|---|
| promote | Real, worth a card (bug, debt, or gap — unverified ideas included) | Draft claim block in the card's origin shape (problem, area, prior), ready for a batched /super-bootstrap:log |
| patch | Real, and the whole fix is a bounded doc-mechanical edit (stale path, dead link, wrong name) | The exact edit: file, old text, new text. Anything wider → promote |
| dup | An open card already covers it | The card ID; plus, when the finding adds a new fact, that fact as a one-line ## Amendment claim — it rides the same batched /super-bootstrap:log (its amended branch appends it to the owning card) |
| needs-investigation | Real-or-not needs a trace reads alone can't settle | The single discriminating question |
| dismiss | Not real, or cost exceeds worth | Your rationale (the gateway bounces a rationale weaker than the scanner's stated reasoning) |
Output contract
Return, concise:
- Coverage line —
{N} findings, {N} verdicts(must match). - Per finding —
{finding ref} → {verdict}: {payload}. - Batch blocks — promote claim blocks and dup Amendment claims grouped ready for one
/super-bootstrap:logdispatch; patch edits grouped by file.
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 · 39 lines · 95 tokens per session scan A 13f3bf387431
triage-report is an agent published in the GitHub repository RockyHong/super-bootstrap (3 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 704 once invoked, about $0.0005 per session on Opus 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 agents, from other repositories
bulwark-fix-validator
Validates fixes against debug report by executing tiered test plan and assessing confidence. Reads validation plan from IssueAnalyzer output. Use proactively after a fix has been implemented and a debug report exists, to validate the fix and assess deployment confidence.
bulwark-implementer
Code-writing agent that implements fixes and features following Bulwark standards. Quality enforced by direct implementer-quality.sh invocation after each Write/Edit. Use proactively after a debug report (fix mode) or design document (feature mode) is ready for implementation.
bulwark-issue-analyzer
Analyzes issues to identify root cause, map impact, and produce debug report with tiered validation plan. Supports both production code bugs and test code issues.
fixer
Bug fixer agent. Picks up open GitHub issues labeled 'bug' or 'seeker', creates a fix branch, implements the fix, runs tests, and raises a PR. Use for automated bug fixing from issue queue.
seeker
Bug seeker agent. Pulls fresh logs from Kubernetes pods, analyzes for errors/crashes/anomalies, and raises GitHub issues with reproduction steps. Use when monitoring production or running maintenance sweeps.
lint-quality
Lint and static analysis agent. Use for enforcing code style, running linters, and checking for common code quality issues. Fast and mechanical.