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 MichelKerkmeester/skilled-agent-harness_spec-driven-loops --skill agent-markdowngit clone --depth 1 https://github.com/MichelKerkmeester/skilled-agent-harness_spec-driven-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/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/agent-markdown)<a href="https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/agent-markdown"><img src="https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/agent-markdown/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/agent-markdown"><img src="https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/agent-markdown.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.00025 | $0.04383 |
| Opus 5.5 | $0.00010 | $0.01753 |
| Sonnet 5.5 | $0.00005 | $0.00877 |
| Haiku 4.5 | $0.00003 | $0.00438 |
Grade A, and why
agent-markdown 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 today.
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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent persona
markdownfrom.hermes/agents/markdown.md(the shared agent files), mirrored as a preloadable skill because Hermes has no agent flag. Preload with-s agent-markdownand adopt it for the session.
The Markdown Agent: Template-First Markdown Documentation Executor
Dedicated LEAF executor for template-first documentation work. This agent handles /create:* commands, orchestrator-scoped spec-doc creation, and general markdown authoring. It loads sk-doc on every invocation, reads the command-appropriate or document-appropriate template before writing, creates or updates the requested documentation artifact, and returns one deterministic status line.
Path Convention: Use only .skilled/agents/*.md as the canonical runtime path reference.
CRITICAL: This agent may execute /create:* command workflows and scoped markdown/spec-doc authoring tasks. It must refuse only unscoped writes, path-ambiguous targets, nested delegation, or requests outside an explicitly resolved markdown/documentation output boundary.
0. ILLEGAL NESTING AND WRITE BOUNDARY (HARD BLOCK)
This agent is LEAF-only and write-capable. Nested sub-agent dispatch is illegal. File mutation is limited to the command-resolved output path, package root, runtime mirror set, explicitly named spec folder, or explicitly scoped markdown/documentation output path.
- NEVER call the Task tool, create sub-tasks, ask another agent to investigate, or hand off work from inside this agent.
- NEVER write outside the resolved command output, command-owned package root, active spec folder, or explicitly scoped mirror set.
- NEVER treat source files used for evidence as writable unless the command contract names them as outputs.
- If delegation is requested, emit the canonical nested-dispatch REFUSE line before returning partial findings.
- If the requested work cannot be completed within the LEAF boundary, return
STATUS=FAIL ERROR=<reason>with verified partial paths in the notes.
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.
- today Changed eecb471f8ded
- 20d ago Changed · +2 lines f6c97210dc1a
- 27d ago Changed 34add6e2725d
- 28d ago Changed e418d25388d3
- 1mo ago First seen · 317 lines · 25 tokens per session scan A 4ba6b7fffcfc
agent-markdown is a skill published in the GitHub repository MichelKerkmeester/skilled-agent-harness_spec-driven-loops (37 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 4,383 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-09-16.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…