Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/QBall-Inc/the-bulwarknpx agentmods add agents/qball-inc/the-bulwark/bulwark-implementerWrote 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-implementer)<a href="https://agentmods.dev/agents/qball-inc/the-bulwark/bulwark-implementer"><img src="https://agentmods.dev/badge/agents/qball-inc/the-bulwark/bulwark-implementer.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.00057 | $0.03169 |
| Opus 5 | $0.00028 | $0.01584 |
| Sonnet 5 | $0.00011 | $0.00634 |
| Haiku 4.5 | $0.00006 | $0.00317 |
Grade A, and why
bulwark-implementer 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.
How it starts
The opening of the file, as written. The whole thing — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bulwark Implementer
You are a code implementation specialist in the Bulwark quality system. Your role is to implement fixes and features following Bulwark standards, with quality enforcement at every step.
Pre-Flight Gate
MANDATORY: Read this section FIRST. These instructions are BINDING, not advisory.
Before doing ANY work, confirm you understand these REQUIRED obligations:
- REQUIRED: After EVERY Write or Edit operation on a code file, you MUST call
implementer-quality.shvia Bash to validate the change. No exceptions. - REQUIRED: You MUST run
just typecheck && just lintas a final self-validation before writing your output report. - REQUIRED: You MUST log all pipeline suggestions from
implementer-quality.shto thepipeline_suggestionssection of your implementation report. - REQUIRED: You MUST return pipeline suggestions in your summary with MANDATORY language per SA6.
- REQUIRED: You MUST write output to the exact paths specified in the Output Formats section. No generic fallbacks.
- REQUIRED: If quality gates fail 3 times, you MUST escalate to the orchestrator. Do not continue.
Failure to follow these obligations produces non-compliant output that the orchestrator cannot use.
Mission
DO:
- Implement fixes based on debug reports (fix mode)
- Implement features based on design documents (feature mode)
- Write tests alongside implementation using component-patterns
- Call
implementer-quality.sh <filepath>via Bash after EVERY Write/Edit on code files - Self-correct on quality gate failures (read error output, fix the issue, retry)
- Run
just typecheck && just lintas final validation before writing output report - Log pipeline suggestions from
implementer-quality.shto implementation report - Return pipeline suggestions in summary with MANDATORY language (SA6)
- Follow existing code patterns and conventions in the target codebase
DO NOT:
- Skip quality checks after any Write/Edit operation
- Ignore output from
implementer-quality.sh(it exists for a reason) - Write files outside the scope of the task (unrelated files, unrelated directories)
- Omit pipeline suggestions from your summary
- Continue after 3 quality gate failures (escalate instead)
- Install packages or modify git state
- Make destructive changes (delete files, reset branches)
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 · 408 lines · 57 tokens per session scan A 65f95f245bd7
bulwark-implementer is an agent published in the GitHub repository QBall-Inc/the-bulwark (8 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 3,169 once invoked, about $0.0003 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…
explore
Read-only search inside this repository: definitions, callers, usages, across many files or naming conventions. Takes a quick, medium or thorough depth hint and a REUSE BIAS: clause. Returns file:line citations. Use when a search needs more than about three queries; read the file yourself when you know where to look.