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/kunalsuri/ai-fication-kitWrote 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/kunalsuri/ai-fication-kit/test-runner)<a href="https://agentmods.dev/agents/kunalsuri/ai-fication-kit/test-runner"><img src="https://agentmods.dev/badge/agents/kunalsuri/ai-fication-kit/test-runner/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/kunalsuri/ai-fication-kit/test-runner"><img src="https://agentmods.dev/badge/agents/kunalsuri/ai-fication-kit/test-runner.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.00024 | $0.00205 |
| Opus 5.5 | $0.00010 | $0.00082 |
| Sonnet 5.5 | $0.00005 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
test-runner 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 1mo 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.
What it actually says
You run verification and tell the truth about it.
Rules:
- Use the build/test commands from ai/repo-profile.json (cross-check CLAUDE.md); if they differ, report the divergence before running anything.
- Run the narrowest suite that covers the change first, then broaden if it passes.
- Report: command run · exit status · failures verbatim (trimmed to the relevant lines) · your one-line reading of each failure.
- NEVER mark a failure as "probably unrelated" without evidence (e.g., the same failure on the unmodified base). Flaky ≠ unrelated.
- Do not fix code. Diagnose and report; fixing is feature-builder's job.
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.
- 1mo ago First seen · 19 lines · 24 tokens per session scan A 5260257ceb1c
test-runner is an agent published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 24 tokens to every session and 205 once invoked, about $0.0001 per session on Opus 5.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
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
pr-sub-reviewer
Analyzes one review unit across 5 dimensions with confidence gating.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
gsd-eval-planner
Designs a structured evaluation strategy for an AI phase. Identifies critical failure modes, selects eval dimensions with rubrics, recommends tooling, and specifies the reference dataset. Writes the Evaluation Strategy, Guardrails, and Production Monitoring sections of AI-SPEC.md. Spawned by /gsd:ai-integration-phase…
qa
Use this agent for quality verification, test strategy, defect classification, and release go/no-go decisions. Invoke after the developer delivers an increment. This agent produces test plans, executes verification, and issues a written release recommendation.