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 ivy00johns/Skill-Madness --skill contract-conformance-loopgit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWrote 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/ivy00johns/skill-madness/contract-conformance-loop)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/contract-conformance-loop"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/contract-conformance-loop.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.1 | $0.00195 | $0.02637 |
| Opus 5 | $0.00097 | $0.01319 |
| Sonnet 5 | $0.00039 | $0.00527 |
| Haiku 4.5 | $0.00019 | $0.00264 |
Grade A, and why
contract-conformance-loop 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 7d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
contract-conformance-loop
A configuration of [
loop-controller]. That skill supplies the loop machinery — primitive selection, the full guardrail stack, state externalization. This skill supplies the two things specific to "build until the spec holds": a fresh-context evaluator as the proof (the [contract-auditor] graded against an authored contract, default-FAIL) and the generator/evaluator split that keeps the builder from grading its own work. Readloop-controllerfor the guardrails; they're inherited, not repeated here.Why
disable-model-invocation: this loop edits and commits code on its own and spends tokens spawning an evaluator subagent each round, until every contract criterion passes. You want to type/contract-conformance-loop(or have the orchestrator dispatch it) — not have Claude silently start an autonomous build loop because a contract happened to exist.
The 5-part contract
| Part | This loop |
|---|---|
| trigger | an authored contract exists ([contract-author] output in contracts/) plus an implementation to build or verify against it, or an explicit /contract-conformance-loop (optionally scoped to one contract) |
| action | ONE iteration: the generator (the builder / role agent) implements or fixes toward one not-yet-passing criterion → a fresh-context evaluator subagent ([contract-auditor], spawned with no Write/Edit) checks ALL criteria against evidence and returns a default-FAIL verdict with per-criterion pass/fail + feedback → failing criteria + feedback feed the next iteration |
| proof | every entry in the criteria JSON has passing evidence confirmed by the fresh-context evaluator (not the builder) — default-FAIL: each criterion starts "passed": false and only the evaluator's verdict, citing evidence, flips it |
| memory | criteria.json (the default-FAIL criteria, one entry per contract criterion), PROGRESS.md (what's done / next), a git checkpoint per criterion turned green |
| stop | the evaluator confirms all criteria pass OR iteration cap OR no-progress for 3 rounds OR budget cap |
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.
- 7d ago First seen · 185 lines · 195 tokens per session scan A 661ba8feec8f
contract-conformance-loop is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed 27d ago), licensed MIT. It adds 195 tokens to every session and 2,637 once invoked, about $0.0010 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-30.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.