Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tmusser/ai-engineering-skillsnpx agentmods add skills/tmusser/ai-engineering-skills/verify-contractWrote 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/tmusser/ai-engineering-skills/verify-contract)<a href="https://agentmods.dev/skills/tmusser/ai-engineering-skills/verify-contract"><img src="https://agentmods.dev/badge/skills/tmusser/ai-engineering-skills/verify-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/tmusser/ai-engineering-skills/verify-contract"><img src="https://agentmods.dev/badge/skills/tmusser/ai-engineering-skills/verify-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.00032 | $0.01330 |
| Opus 5 | $0.00016 | $0.00665 |
| Sonnet 5 | $0.00006 | $0.00266 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
verify-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 9d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Contract
Purpose
Prove the task actually works and leave durable evidence.
Verification also checks that the implementation did not exceed the behavioral contract or frozen write boundary merely because the extra work looked reasonable.
When to use
After implementation, tests, bug fixes, data runs, or smoke checks.
Inputs
- Task name
SPEC.mdacceptance criteria, non-goals, constraints, and invalid-if rules- Optional persisted
SCOPE.mdplus its frozen Git base - Commands run or to run
- Changed files
- Evidence to record
- Known risks or untested areas
Workflow
-
Update VERIFY.md with date + task name.
-
Record commands run as short evidence entries with command, exit code, relevant output, interpretation, acceptance criterion covered, and remaining uncertainty. Keep each entry concise and auditable.
-
When
SCOPE.mdandscripts/scope_gate.pyare available, run:python scripts/scope_gate.py --base <frozen-base>Record its status and relevant violations or review triggers. A scope-gate
FAILprevents PASS.REVIEW_REQUIREDalso prevents PASS until the named review is resolved. -
If
scripts/verify_gate.pyis available, run it before marking verification complete. If repeated iterations were used, check for a loop contract, budget, ledger, revert rule, and stop condition before calling the work done. -
List changed files.
-
Run the spec ceiling check against the implemented behavior and diff.
-
Note working directory / environment assumptions if relevant.
-
Link artifacts/screenshots if relevant (supporting evidence only; automated checks preferred).
-
Note what was not tested and remaining risks.
-
Name the next safest task.
Verify gate
Status: PASS | FAIL | REVIEW_REQUIRED
- PASS only when contract probes pass, the scope gate passes when a persisted scope exists, no diff guard requires review, and no spec ceiling violation is present.
- FAIL when behavior or contract probes fail, the scope gate fails, or an explicit non-goal / invalid-if rule was violated.
- REVIEW_REQUIRED when behavior passes but evidence integrity is questionable, the scope gate requires review, or plausible extra behavior exceeds the written acceptance criteria and intent is ambiguous.
- REVIEW_REQUIRED is not the same as functional failure.
- If repeated iterations occurred without a loop contract, use REVIEW_REQUIRED.
- If loop budget, ledger, revert rule, or stop condition was violated, use REVIEW_REQUIRED or FAIL depending on whether the behavior contract failed.
- Do not treat loop activity as success merely because the final output looks plausible.
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.
- 9d ago First seen · 169 lines · 32 tokens per session scan A 9b2a0e9d60ff
verify-contract is a skill published in the GitHub repository tmusser/ai-engineering-skills (4 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,330 once invoked, about $0.0002 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
tdd
Use this skill to practice test-driven development — writing tests before implementation, using tests to drive design, and validating implementation against pre-written tests. Activates when implementing new functionality, refactoring code, or fixing bugs where regression coverage is needed.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
skill-release-gate
Evaluate an Agent Skill bundle for structural integrity, trigger quality, artifact improvement, script correctness, safety, installed-tree integrity, and target-host portability before release.
nemo-automodel-recipe-development
Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.
mcore-testing
Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.
i4h-catheter-navigation-e2e
End-to-end smoke for catheter navigation covering setup, digital twin, DRR, and unit tests. Use when asked to run the full catheter workflow smoke or demo the v0.7 pipeline.