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 instructions/formin/spec-kit-harness/agents-mdgit clone --depth 1 https://github.com/formin/spec-kit-harnessWrote 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/instructions/formin/spec-kit-harness/agents-md)<a href="https://agentmods.dev/instructions/formin/spec-kit-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/formin/spec-kit-harness/agents-md.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.00078 | $0.00078 |
| Opus 5 | $0.00039 | $0.00039 |
| Sonnet 5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
spec-kit-harness AGENTS.md 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:
- spec-kit-harness CLAUDE.md — 100% identical, 0 lines differ
What it actually says
OpenWiki
This repository has documentation located in the /openwiki directory.
Start here:
OpenWiki includes repository overview, architecture notes, command reference, and operations guidance.
When working in this repository, read the OpenWiki quickstart first, then follow its links to the relevant architecture, command, and operations 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.
- 3d ago First seen · 12 lines · 78 tokens per session scan A 054fb706a05d
spec-kit-harness AGENTS.md is an instructions file published in the GitHub repository formin/spec-kit-harness (5 stars, last pushed 2mo ago), licensed MIT. It adds 78 tokens to every session, about $0.0004 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 instructions, from other repositories
spec-kit-archive copilot-instructions.md
Instructions for stn1slv/spec-kit-archive, covering fixture project — copilot instructions, active technologies and recent changes.
spec-driven-steroids AGENTS.md
Instructions for lindoelio/spec-driven-steroids, covering agents.md, project identity, technology stack, essential commands and agent constraints.
loadout go.instructions.md
Go Engineering Instructions (CLI + API, framework-agnostic).
loadout shell.instructions.md
Shell Script Engineering Instructions (Bash, CLI wrappers, automation).
loadout playwright-typescript.instructions.md
Playwright TypeScript Test Generation Instructions.
loadout playwright-python.instructions.md
Playwright Python Test Generation Instructions.