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 David405/harness-kit --skill sprint-contractgit clone --depth 1 https://github.com/David405/harness-kitWrote 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/david405/harness-kit/sprint-contract)<a href="https://agentmods.dev/skills/david405/harness-kit/sprint-contract"><img src="https://agentmods.dev/badge/skills/david405/harness-kit/sprint-contract/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/david405/harness-kit/sprint-contract"><img src="https://agentmods.dev/badge/skills/david405/harness-kit/sprint-contract.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.00082 | $0.00570 |
| Opus 5.5 | $0.00033 | $0.00228 |
| Sonnet 5.5 | $0.00016 | $0.00114 |
| Haiku 4.5 | $0.00008 | $0.00057 |
Grade A, and why
sprint-contract 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 2mo 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.
What it actually says
Sprint contract
Kit-owned. Edit in the harness-kit repo, not in the consumer repo.
Contract before code. No test or production code exists before the human approves this and confirms the branch name.
When to use
Any non-trivial change. Trivial fixes (typo, one-line config) may use a condensed contract
if AGENTS.md allows it.
When not to use
A Solidity security review → solidity-audit. A periodic quality audit → code-audit.
Steps
- Pick one work-type profile. It decides which quality gates are in force and which are N/A.
- Scope, both halves. What this sprint delivers, and explicitly what it does not.
- Propose a feature branch. Ask: "Confirm feature branch
<name>(yes / or another name)." Do not create or check out anything until the human replies. Never implement on the default branch. - Lock decisions, or record them Open with an owner and a needed-by.
- Tests first. Name the failing tests and the repo's real verify commands from
AGENTS.md. For behaviour-preserving refactors, characterization tests replace product TDD. - Impact map, every path marked
[GROUNDED](verified in the repo) or[EDUCATED](re-verify first). - Falsifiable success criteria — command output, status and body, a revert, a log field. Never "works correctly" or "clear error".
- Blocking questions with a recommendation each, so approval is one message.
Opening the PR
Contracts stay local (skills/.harness/ is gitignored). When the human asks to publish, use
the create-pull-request skill — a detailed, product-facing PR body only.
Do not paste this contract, feature ledger IDs, harness-review output, or contract HTML markers into the GitHub PR title or body. Review runs in chat before the PR is opened.
No tool attribution in the title, body, or commit messages, and a commit's author is the human.
Form
templates/SPRINT_CONTRACT.md
What ships with it
1 file 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.
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.
- 2mo ago First seen · 54 lines · 82 tokens per session scan A 16d4a51b804e
sprint-contract is a skill published in the GitHub repository David405/harness-kit (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 82 tokens to every session and 570 once invoked, about $0.0003 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-08-31.
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…