Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MichelKerkmeester/skilled-agent-harness_spec-driven-loopsnpx agentmods add skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-agentWrote 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/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-agent)<a href="https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-agent"><img src="https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-agent/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/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-agent"><img src="https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.04190 |
| Opus 5 | $0.00013 | $0.02095 |
| Sonnet 5 | $0.00005 | $0.00838 |
| Haiku 4.5 | $0.00003 | $0.00419 |
Grade A, and why
sk-create-agent 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 6d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Agent - Runtime Persona Authoring
create-agent is the sk-doc workflow packet for creating or updating one runtime agent markdown file. The executable contract lives here: decide whether an agent is the right component, place it in the active runtime directory, author current frontmatter and authority boundaries, then validate before delivery.
Use references/README.md (the overflow route map) and assets/agent-template.md only for deeper examples, exhaustive variants, and long-form reference detail. Do not make those files the primary workflow contract.
1. WHEN TO USE
Activation Triggers
Use this workflow when the request involves:
- Creating a new OpenCode or Claude Code agent file.
- Updating an agent's frontmatter, permissions, authority boundary, workflow, verification contract, or anti-patterns.
- Converting a durable role description into a runtime persona with explicit authority and tool policy.
- Deciding whether the requested component should be an agent, skill, or command.
- Running or supporting
/create:agent.
Keyword triggers: create agent, /create:agent, OpenCode agent, Claude Code agent, agent file, new agent, agent persona, agent frontmatter, permission object, authority boundary, agent template, runtime agent directory, agent and paired.
Create an agent only when the system needs a stable named persona with explicit tool permissions, denied capabilities, behavioral constraints, orchestration authority, or reusable execution posture.
When NOT to Use
Use another sk-doc packet when:
- The request needs reusable knowledge, standards, templates, or long-form workflow guidance. Use
create-skill. - The request needs a slash-command entry point without a new runtime persona. Use
create-command. - The request needs a README, install guide, feature catalog, manual testing playbook, benchmark package, flowchart, or changelog. Use
create-readme,create-feature-catalog,create-manual-testing-playbook,create-benchmark,create-flowchart, orcreate-changelog. - The request audits, validates, scores, or optimizes an existing agent document. Use
create-quality-control.
What ships with it
17 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.
- assets/agent-template.md 35 KB
- changelog/v1.0.0.0.md 1.7 KB
- changelog/v1.0.1.0.md 1.7 KB
- changelog/v1.0.1.1.md 940 B
- changelog/v1.0.1.2.md 1.7 KB
- manual-testing-playbook/body-validation/leaf-denies-delegation.md 4.9 KB
- manual-testing-playbook/body-validation/required-agent-sections.md 5.6 KB
- manual-testing-playbook/component-choice/named-runtime-persona.md 5.5 KB
- manual-testing-playbook/component-choice/reusable-knowledge-stays-a-skill.md 5.2 KB
- manual-testing-playbook/manual-testing-playbook.md 11 KB
- manual-testing-playbook/runtime-contract/claude-tools-allow-list.md 5.1 KB
- manual-testing-playbook/runtime-contract/opencode-permission-object.md 5.0 KB
- README.md 10 KB
- references/agent-vs-skill-vs-command.md 3.6 KB
- references/common-pitfalls.md 3.0 KB
- references/permission-design.md 3.5 KB
- references/README.md 3.3 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.
- 6d ago Changed · -1 lines a9b4d2350a6e
- 8d ago First seen · 350 lines · 26 tokens per session scan A 4d58c69c58f4
sk-create-agent is a skill published in the GitHub repository MichelKerkmeester/skilled-agent-harness_spec-driven-loops (35 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 4,190 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…