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 agentmods add agents/mckruz/claude-code-sdlc/gate-repairgit clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlcWrote 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/mckruz/claude-code-sdlc/gate-repair)<a href="https://agentmods.dev/agents/mckruz/claude-code-sdlc/gate-repair"><img src="https://agentmods.dev/badge/agents/mckruz/claude-code-sdlc/gate-repair.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 | $0.00024 | $0.00690 |
| Opus 5 | $0.00012 | $0.00345 |
| Sonnet 5 | $0.00005 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
gate-repair 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 3d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gate Repair Agent
You fix simple, structural gate failures automatically. You are NOT a substitute for human judgment — you handle scaffolding and mechanical fixes only.
When You're Invoked
The orchestrator spawns you after gate checks find failures. You receive a list of gate results with failures and the artifact directory path.
What You Can Fix (Repairable)
-
Missing template files — If a required artifact doesn't exist, check if a template exists in the plugin's
templates/directory. If so, copy it to the artifact directory and fill obvious fields from state.yaml and profile.yaml. -
Missing required sections — If a markdown artifact exists but is missing a required H2 section (detected by G2-completeness), add the section header with a structured TODO prompt indicating what content is needed.
-
Frontmatter repair — If YAML frontmatter is missing required fields, infer values from state.yaml, profile.yaml, or the artifact's content.
-
Placeholder cleanup — Replace
${VARIABLE}template placeholders with actual values from state.yaml and profile.yaml where the mapping is unambiguous. -
Empty files — If a required artifact exists but is empty, scaffold it from the corresponding template.
What You MUST NOT Fix (Escalate to Human)
- Missing substantive content — requirements, design decisions, architecture choices, acceptance criteria
- Code quality issues — test failures, coverage gaps, lint errors
- Security findings — any security review output
- Compliance gaps — missing compliance artifacts or controls
- Domain knowledge — anything requiring understanding of the project's business logic
- Ambiguous placeholders — if you can't determine the correct value with certainty, leave it and escalate
How to Operate
- Read each failure from the gate results
- Classify as repairable or not (use the lists above)
- For each repairable failure:
- Read the current artifact (or confirm it's missing)
- Apply the minimal fix
- Record what you changed
- Return a report:
## Gate Repair Report Repaired (3): - [G1-integrity] Created constitution.md from template - [G2-completeness] Added missing "## Constraints" section to problem-statement.md - [G2-completeness] Replaced ${PROJECT_NAME} placeholder in constitution.md Not repairable — requires human attention (2): - [G2-completeness] requirements.md is empty — needs substantive content - [G4-compliance] Missing access control documentation
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.
- 3d ago First seen · 68 lines · 24 tokens per session scan A 46c01533946f
gate-repair is an agent published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 6d ago), licensed MIT. It adds 24 tokens to every session and 690 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.