contract-auditor

contract-auditor is a skill for Claude Code from ivy00johns/Skill-Madness. It costs 55 tokens per session (2,035 once invoked), scanned A, original, MIT.

A code review step that compares built software with written integration contracts, such as rules for APIs, stored data, and shared types.

In plain words
What is it for?
Checking implementations against machine-readable contracts and writing findings to a contract-audit.md file for a later quality check.
Why use it?
It finds disagreements between planned interfaces and actual code before integration testing, when they are easier to correct. It is intended for orchestrated multi-agent projects, not one-off development.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is **Pipeline position.** Runs after implementation agents complete. Reads contracts from `contract-author` (including the flat `contracts/types.<ext>`). Writes fi.

Part of the skill-madness plugin — 80 skills shipped together

Good fit Checking implementations against machine-readable contracts and writing findings to a contract-audit.md file for a later quality check.

Compare 6 skills from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ivy00johns/Skill-Madness
agentmods
npx agentmods add skills/ivy00johns/skill-madness/contract-auditor

Made for: Claude Code.

Or install skill-madness, the plugin that ships this one along with the rest of its 80 skills.

Wrote 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.

agentmods badge for contract-auditor

README.md
[![agentmods](https://agentmods.dev/badge/skills/ivy00johns/skill-madness/contract-auditor/github.svg)](https://agentmods.dev/skills/ivy00johns/skill-madness/contract-auditor)
Your own site
<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/contract-auditor"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/contract-auditor/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.

agentmods 80×15 button for contract-auditor

Your own site · 80×15
<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/contract-auditor"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/contract-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,035 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.02035
Opus 5 $0.00028 $0.01018
Sonnet 5 $0.00011 $0.00407
Haiku 4.5 $0.00006 $0.00203

Measured 9d ago against content hash 7782dc1a582d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

contract-auditor 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.

skills/contracts/contract-auditor/SKILL.md · 182 lines

How it starts

The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Contract Auditor

Pipeline position. Runs after implementation agents complete. Reads contracts from contract-author (including the flat contracts/types.<ext>). Writes findings to contract-audit.md at the repo root, consumed by qe-agent. When contract-conformance-loop dispatches you as its fresh-context evaluator, you are spawned with no Write/Edit tools (Read/Grep/Bash only) — the Write in your frontmatter is for standalone contract-audit.md output only, and the loop depends on you being unable to "fix" a failure by lowering the bar.

Audit implementations against their integration contracts. You find mismatches between what was contracted and what was built — before integration testing begins.

When this skill applies

This skill assumes a contract-first multi-agent build model:

  • An orchestrator dispatches role-agents in parallel
  • Each role-agent consumes a machine-readable contract from /contracts/
  • qe-agent gates the build via qa-report.json

For single-agent or ad-hoc work, this skill is not the right tool.

Role

You are the contract auditor. You compare the actual implementation code against the defined contracts (API, data layer, shared types) and report every deviation. You run after implementation agents report done but before the QE agent begins integration testing.

This is a static analysis pass — you read code and contracts, you don't run the application.

Inputs

From the lead:

  • contracts/ — the contract-author's output files. Look for:
    • contracts/openapi.yaml — API contract (endpoints, schemas, error envelopes)
    • contracts/data-layer.yaml — data layer contract (function signatures, storage semantics)
    • contracts/types.<ext> — shared type definitions, a single flat file (contracts/types.ts, contracts/types.py, or contracts/types.json), not a directory. This is the exact path contract-author writes.
    • If contracts are in a different format or location, the lead will specify.
  • agent_ownership — which agent owns which files, so you can attribute mismatches to the responsible agent
  • tech_stack — language and framework, so you know what route/handler patterns to search for
  • service_map — service names and source directories (don't assume backend/src/ or frontend/src/)

Read the full file on GitHub · 182 lines

Files

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.

Changes

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.

  1. 9d ago First seen · 182 lines · 55 tokens per session scan A 7782dc1a582d

Subscribe to this mod's changes

contract-auditor is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 2,035 once invoked, about $0.0003 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.