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 n-n-code/n-n-code-skills --skill development-contract-repo-overlay-templategit clone --depth 1 https://github.com/n-n-code/n-n-code-skillsWrote 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/n-n-code/n-n-code-skills/development-contract-repo-overlay-template)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/development-contract-repo-overlay-template"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/development-contract-repo-overlay-template/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/n-n-code/n-n-code-skills/development-contract-repo-overlay-template"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/development-contract-repo-overlay-template.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.00071 | $0.00921 |
| Opus 5 | $0.00036 | $0.00461 |
| Sonnet 5 | $0.00014 | $0.00184 |
| Haiku 4.5 | $0.00007 | $0.00092 |
Grade A, and why
development-contract-repo-overlay-template 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 4d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Contract Repo Overlay Template
This skill documents the expected shape of the repo-local overlay that a target repository should have after adopting the development contract system. It is not guidance for this skills repository itself, which only stores the reusable skills.
Use target policy as the source for contract mechanics within the host's instruction hierarchy. Keep an unresolved policy/documentation conflict visible; do not decide it merely by preferring whichever file was opened first.
Use this skill when
- authoring or revising the repo-local overlay generated for a target repository
- checking that overlay guidance matches the target repo's policy file, checker command, lifecycle helper, plan directory, and validation profiles
- deciding which repo-specific literals belong in the overlay versus the policy file
Do not use this skill as the primary process for ordinary implementation work
inside a target repo. For that, use development-contract-process plus the
target repo's actual local overlay and implementation skill.
Repo overlay workflow
- Select findings, draft, or apply from the request. Findings and conversation drafts do not authorize repository writes.
- Read existing overlays and the policy, checker, helper, and profile definitions that establish the target's actual commands and paths.
- Write only the overlay's local bindings and exceptional human guidance. Refer
to
development-contract-processwhen it is available to the target agent; otherwise include the minimum operator steps needed to use the repo's system. - During authorized application, follow the target's existing contract process if changing the overlay is itself substantive. Do not require an unrelated implementation or record update merely to produce a draft.
- Check the overlay against the real files and safe checker modes. Report observed commands separately from proposed or unrun commands.
Decision rules
- Treat the target repo's policy file as the source of truth for what is substantive in that repo.
- Do not leave a substantive change without a non-template plan update.
- Use the repo's lifecycle helper with its supersede option when superseding a record so the replacement link is updated with the move.
- Keep the repo overlay thin: change policy data first, then only add prose when the repo needs extra human guidance that policy cannot express.
- Resolve policy/documentation mismatches from evidence within authorized scope; report unresolved decisions rather than silently changing policy.
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.
- 4d ago Changed · +2 lines 019b9e6e3c5c
- 9d ago First seen · 89 lines · 71 tokens per session scan A 14bbdb33b30d
development-contract-repo-overlay-template is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 921 once invoked, 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 skills, from other repositories
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
plan-feature
Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling. Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".
audit-docs
Audit cross-document coherence: docs ↔ roadmap ↔ code ↔ fix index ↔ issues. Finds drift — features in docs/ not in the roadmap (or vice versa), fix-index entries already merged/closed, broken documentation-map links, dependency cycles, artifacts in the wrong language, naming-convention violations — and reports them…
fold-findings
Repair persisted fix-now findings in compatible atomic batches: root-cause fixes, green gate, commit/push, and per-row folded: yes updates. Never reclassify or substitute backlog notes. Triggers: "fold-findings", "fix the review findings", "repair audit blockers".