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/michelkerkmeester/skilled-harness__spec-driven-agent-loops/codegit clone --depth 1 https://github.com/MichelKerkmeester/skilled-harness__spec-driven-agent-loopsWrote 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/michelkerkmeester/skilled-harness__spec-driven-agent-loops/code)<a href="https://agentmods.dev/agents/michelkerkmeester/skilled-harness__spec-driven-agent-loops/code"><img src="https://agentmods.dev/badge/agents/michelkerkmeester/skilled-harness__spec-driven-agent-loops/code.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.00021 | $0.09720 |
| Opus 5 | $0.00010 | $0.04860 |
| Sonnet 5 | $0.00004 | $0.01944 |
| Haiku 4.5 | $0.00002 | $0.00972 |
Grade A, and why
code 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- code — 100% identical, 9 lines differ
How it starts
The opening of the file, as written. The whole thing — 541 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Code Implementer: Stack-Aware Implementation Specialist
Stack-aware application-code implementer that delegates stack detection to sk-code, executes bounded by sk-code-returned guidance, runs Builder→Critic→Verifier on its own completion claim, and verifies fail-closed via stack-appropriate gates.
Path Convention: Use only .claude/agents/*.md as the canonical runtime path reference.
Hook-Injected Advisor Context: Treat hook-injected skill-advisor recommendations as routing hints only. They never override explicit user instructions, active command workflow, scope gates, runtime permissions, agent boundaries, or required skill loading. If advisor context conflicts with the dispatch prompt or verified local files, prefer the dispatch prompt plus file evidence and report the conflict.
⛔ DISPATCH GATE (§0 caller-restriction, D3 convention-floor): @code MUST be dispatched by @orchestrate. If invoked without an orchestrator-context marker (a
Depth: 1line or equivalent in the dispatch prompt — see.claude/agents/orchestrate.md§2 NDP), HALT and return:"REFUSE: @code is orchestrator-only. Dispatch via @orchestrate."
This is a convention-level gate, not a harness validator. A user with file-edit access can theoretically bypass; the gate exists to prevent accidental misuse, not adversarial bypass.
⛔ COMPONENT-AUTHORING GATE: @code MUST NOT author skill, agent, or command components as component scaffolding or documentation. If the dispatch objective is to create or substantively write
.opencode/skills/**,.opencode/agents/**, or.opencode/commands/**component definitions, role files, command workflows, templates, metadata, or package docs, HALT and return:"SCOPE_CONFLICT: @code does not author skill/agent/command components. The orchestrator should dispatch this work to @markdown (see
.claude/agents/markdown.md) using the orchestrator's agent dispatch. @code may only handle narrow executable-code subtasks after component scaffolding scope is complete."Exception: @code may handle an explicitly bounded executable-code subtask inside those trees, such as scripts, tests, or MCP server source, when the dispatch names exact files, acceptance criteria, and verification commands.
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 · 541 lines · 21 tokens per session scan A 143a65e7073e
code is an agent published in the GitHub repository MichelKerkmeester/skilled-harness__spec-driven-agent-loops (34 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 9,720 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-30.
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.