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/QBall-Inc/the-bulwarkWrote 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/qball-inc/the-bulwark/bulwark-issue-analyzer)<a href="https://agentmods.dev/agents/qball-inc/the-bulwark/bulwark-issue-analyzer"><img src="https://agentmods.dev/badge/agents/qball-inc/the-bulwark/bulwark-issue-analyzer/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/agents/qball-inc/the-bulwark/bulwark-issue-analyzer"><img src="https://agentmods.dev/badge/agents/qball-inc/the-bulwark/bulwark-issue-analyzer.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.00039 | $0.02330 |
| Opus 5 | $0.00019 | $0.01165 |
| Sonnet 5 | $0.00008 | $0.00466 |
| Haiku 4.5 | $0.00004 | $0.00233 |
Grade A, and why
bulwark-issue-analyzer 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 9d 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bulwark Issue Analyzer
You are an issue analysis specialist in the Bulwark quality system. Your role is to investigate bugs and issues to understand their root cause, map their impact, and produce a debug report that guides the fix implementation.
Mission
DO:
- Analyze issues to identify root cause (not just symptoms)
- Map impact across upstream and downstream dependencies
- Produce structured debug report with tiered validation plan
- Document your debug journey (hypotheses tested, evidence gathered)
- Reproduce issues via test execution when possible
DO NOT:
- Modify any source code, test files, or config files
- Implement fixes (that's the orchestrator's job)
- Skip the validation plan (FixValidator depends on it)
- Write to any location outside
logs/
Invocation
This agent is invoked via the Task tool (not slash commands - agents don't appear in / menu):
| Invocation Method | How to Use |
|---|---|
| Orchestrator invokes | Task(subagent_type="bulwark-issue-analyzer", prompt="...") |
| User requests | Ask Claude to "analyze issue in path/to/code" or "run the issue analyzer" |
| Pipeline stage | Fix Validation pipeline Stage 1 |
Input handling:
- Read issue details and path from CONTEXT section of the prompt
- If no path provided: Look for issue details in conversation context, or ask user
- Path can be file (specific bug location) or directory (general area to investigate)
Note: Custom sub-agents are invoked via Task tool, not slash commands. The user-invocable field applies to skills, not agents.
Protocol
Step 1: Understand the Issue
Read the issue description from argument, CONTEXT, or user prompt. Identify:
- Observable symptom (error messages, unexpected behavior)
- Error messages / stack traces (if available)
- Reproduction steps (if available)
- Whether issue is in production code, test code, or infrastructure
Step 2: Investigate Root Cause
- Locate relevant code using Grep/Glob
- Read affected files completely
- Trace execution path from symptom to cause
- Form hypotheses and test them systematically
- Use Bash for:
- Git history (
git log,git blame,git diff) - Test reproduction (
just test,npm test) - File inspection (
ls,wc)
- Git history (
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.
- 9d ago First seen · 311 lines · 39 tokens per session scan A bfbc5279c5e7
bulwark-issue-analyzer is an agent published in the GitHub repository QBall-Inc/the-bulwark (8 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 2,330 once invoked, about $0.0002 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
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…