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 skills add QBall-Inc/the-bulwark --skill code-reviewgit 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/skills/qball-inc/the-bulwark/code-review)<a href="https://agentmods.dev/skills/qball-inc/the-bulwark/code-review"><img src="https://agentmods.dev/badge/skills/qball-inc/the-bulwark/code-review.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.00061 | $0.04268 |
| Opus 5 | $0.00030 | $0.02134 |
| Sonnet 5 | $0.00012 | $0.00854 |
| Haiku 4.5 | $0.00006 | $0.00427 |
Grade A, and why
code-review 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 — 472 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Comprehensive code review with four independently-referenceable sections. Runs static tools first (fail fast), then applies LLM judgment for patterns tools cannot catch.
When to Use This Skill
Load this skill when the user request matches ANY of these patterns:
| Trigger Pattern | Example User Request |
|---|---|
| Code review | "Review this code", "Check my changes", "Code review for PR" |
| Security review | "Check for security issues", "Find vulnerabilities", "OWASP audit" |
| Type safety check | "Find any usage", "Check type safety", "Null handling issues?" |
| Quality check | "Is this code clean?", "Check code quality", "Standards compliance" |
DO NOT use for:
- Running tests (use
just test) - Auditing test quality (use
test-auditskill) - Debugging issues (use
issue-debuggingskill) - Performance profiling (requires runtime analysis)
Dependencies
This skill references supporting files. Understanding what's required vs optional ensures consistent execution.
| Category | Files | Requirement | When to Load |
|---|---|---|---|
| Pattern references | references/{section}-patterns.md |
REQUIRED | Always load for each enabled section |
| Framework patterns | frameworks/{detected}.md |
CONDITIONALLY REQUIRED | If framework detected → MUST load; if not detected → skip |
| Examples | examples/anti-patterns/*.ts, examples/recommended/*.ts |
OPTIONAL | For calibration on ambiguous cases; kept for model portability |
| Diagnostic schema | references/diagnostic-schema.md |
REQUIRED for Phase 3 | When emitting the diagnostic log (full schema, field rules, examples, Stage-5 aggregation) |
Fallback behavior:
- If framework detected → Loading
frameworks/{name}.mdis REQUIRED - If no framework detected → Skip framework patterns entirely (do not load
generic.md) - If a referenced file is missing → Note in diagnostic log, continue with available patterns
What ships with it
23 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/anti-patterns/linting.ts 4.7 KB runs code
- examples/anti-patterns/security.ts 2.6 KB runs code
- examples/anti-patterns/standards.ts 4.9 KB runs code
- examples/anti-patterns/type-safety.ts 2.8 KB runs code
- examples/recommended/linting.ts 5.2 KB runs code
- examples/recommended/security.ts 4.4 KB runs code
- examples/recommended/standards.ts 5.9 KB runs code
- examples/recommended/type-safety.ts 3.9 KB runs code
- frameworks/angular.md 4.2 KB
- frameworks/django.md 5.0 KB
- frameworks/express.md 4.8 KB
- frameworks/fastapi.md 8.5 KB
- frameworks/flask.md 5.8 KB
- frameworks/generic.md 4.2 KB
- frameworks/react.md 3.4 KB
- frameworks/vue.md 4.3 KB
- references/diagnostic-schema.md 7.0 KB
- references/linting-patterns.md 5.4 KB
- references/security-patterns.md 4.8 KB
- references/standards-patterns.md 7.4 KB
- references/type-safety-patterns.md 4.2 KB
- templates/output-direct.yaml 5.1 KB
- templates/output-pipeline.yaml 5.1 KB
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 · 472 lines · 61 tokens per session scan A d63cbff2bc15
code-review is a skill published in the GitHub repository QBall-Inc/the-bulwark (8 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 4,268 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 skills, from other repositories
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
card-review
Internal skill for onboard's semantic review gate. After the deterministic validation gate (which catches invented symbols / hash drift / secrets), this skill drives a sampled claude -p pass that checks whether the TLDR and role are DIRECTIONALLY ACCURATE given the file's structure and head snippet. The deterministic…
adversarial-reviewer
Use when you want a genuinely critical review of recent changes — before merging a PR, after a sprint, or when you suspect the review is being too agreeable. Forces perspective shifts through three hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer. Triggers on…
triage-report
Drain the .review/ report queue. Resolves un-triaged scan/audit reports (producer-agnostic — check-docs-consistency and any other scanner), dispatches the triage-report subagent (Sonnet) one report at a time for per-finding dispositions (promote / patch / dup / needs-investigation / dismiss), then the gateway absorbs…
review-ticket
Use as a reviewer agent to review another agent's inreview ticket — never your own. Judge whether each acceptance criterion is genuinely met and the change is sound, then record an ADVISORY verdict (per-AC evidence + an overall RECOMMEND APPROVE / RECOMMEND CHANGES line) via the scoped Dispatch MCP, leaving the ticket…