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 test-auditgit 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/test-audit)<a href="https://agentmods.dev/skills/qball-inc/the-bulwark/test-audit"><img src="https://agentmods.dev/badge/skills/qball-inc/the-bulwark/test-audit/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/skills/qball-inc/the-bulwark/test-audit"><img src="https://agentmods.dev/badge/skills/qball-inc/the-bulwark/test-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 523 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00000 | $0.05660 |
| Opus 5 | $0.00000 | $0.02830 |
| Sonnet 5 | $0.00000 | $0.01132 |
| Haiku 4.5 | $0.00000 | $0.00566 |
Grade A, and why
test-audit 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 10d 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 — 556 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Audit
User-facing entry point for test suite quality auditing. Orchestrates classification, mock detection, and synthesis stages to identify T1-T4 violations and trigger automatic rewrites when required.
When to Use This Skill
Load this skill when the user request matches ANY of these patterns:
| Trigger Pattern | Example User Request |
|---|---|
| Test quality audit | "Audit my tests", "Check test quality", "Review test suite" |
| Mock detection | "Find mock violations", "Check for T1 violations", "Are my tests over-mocked?" |
| Test effectiveness | "How effective are my tests?", "Are my tests real or mocked?" |
| After writing tests | "I just wrote tests for X, can you audit them?" |
| CI/CD integration | "Add test audit to pipeline", "Validate tests before merge" |
DO NOT use for:
- Running tests (use
just test) - Writing new tests (implement directly)
- General code review (use
code-reviewskill) - Debugging test failures (use
issue-debuggingskill)
Pre-Flight Gate (BLOCKING)
STOP. Before ANY analysis, you MUST acknowledge what this skill requires.
This skill uses a multi-stage pipeline with sub-agents. You are the orchestrator, NOT the executor.
What You MUST Do
-
Run Stage 0 AST scripts before any LLM stages:
just verify-count {target}→/tmp/claude/ast-verify-count.jsonjust skip-detect {target}→/tmp/claude/ast-skip-detect.jsonjust ast-analyze {target}→/tmp/claude/ast-data-flow.json
-
Select mode based on file count and threshold (default 5)
-
Spawn sub-agents for each applicable stage:
- Stage 1 (Scale mode only): Classification →
Task(subagent_type="general-purpose", model="haiku", ...) - Stage 2: Mock Detection →
Task(subagent_type="general-purpose", model="sonnet", ...) - Stage 3: Synthesis →
Task(subagent_type="general-purpose", model="sonnet", ...)
- Stage 1 (Scale mode only): Classification →
-
Write outputs to logs/:
logs/test-classification-{YYYYMMDD-HHMMSS}.yaml(Scale mode only)logs/mock-detection-{YYYYMMDD-HHMMSS}.yamllogs/test-audit-{YYYYMMDD-HHMMSS}.yamllogs/diagnostics/test-audit-{YYYYMMDD-HHMMSS}.yaml
What ships with it
14 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.
- references/known-limitations.md 2.7 KB
- references/priority-classification.md 889 B
- references/prompts/deep-mode-detection.md 4.6 KB
- references/prompts/synthesis.md 3.0 KB
- references/rewrite-instructions.md 2.3 KB
- references/schemas/audit-output.yaml 4.7 KB
- references/schemas/diagnostic-output.yaml 1.6 KB
- references/two-gate-logic.md 1.2 KB
- scripts/data-flow-analyzer.ts 14 KB runs code
- scripts/integration-mock-detector.ts 14 KB runs code
- scripts/package.json 457 B
- scripts/skip-detector.ts 5.8 KB runs code
- scripts/tsconfig.json 315 B
- scripts/verification-counter.ts 7.4 KB runs code
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.
- 10d ago First seen · 556 lines · 0 tokens per session scan A 8279564b3c6f
test-audit is a skill published in the GitHub repository QBall-Inc/the-bulwark (8 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,660 tokens. 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
enterprise-forge
Adversarial code review with mechanical checks, contract probing, and 5 adversarial lenses. Bugs recycle to contract for full TDD treatment. 3-fail circuit breaker prevents infinite loops. Use after enterprise-review.
uw-code-review
Pre-commit code quality review for Unity C# code. Checks against Rules, CODINGSTANDARDS.md, NAMINGCONVENTIONS.md, and GDD Gherkin test coverage. Use when code has been written and tests are passing but before committing. Runs automatically at Step 8.5 of /uw-cmd-implement-feature. Triggers on "review this code"…
Pair Programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
codex-loop
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
codex-ab
Run an A/B codex review experiment — holistic codex review vs 3 focused dimension passes (security, ecto, liveview) on the branch diff, classify findings, report a panel-value verdict. Use when the branch is fresh, before any codex review runs.
ln-21-documentation-auditor
Audits documentation and comments for trustworthy claims, coverage, and discoverability. Not for code, test, or architecture audits.