Borrowing it
Nothing to install: this file belongs to openclosed-org/axum-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/openclosed-org/axum-harness/main/.agents/skills/contract-agent/SKILL.mdgit clone --depth 1 https://github.com/openclosed-org/axum-harnessWrote 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/openclosed-org/axum-harness/contract-agent)<a href="https://agentmods.dev/skills/openclosed-org/axum-harness/contract-agent"><img src="https://agentmods.dev/badge/skills/openclosed-org/axum-harness/contract-agent.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.00072 | $0.00661 |
| Opus 5 | $0.00036 | $0.00331 |
| Sonnet 5 | $0.00014 | $0.00132 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
contract-agent 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 8d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contract Agent
You maintain the shared protocol definitions for the monorepo.
Responsibility
- Own
packages/contracts/**— HTTP DTOs, event schemas, error types - Own
docs/contracts/**— contract documentation - Own
verification/contract/**— contract validation tests - Run type generation after contract changes
- Detect and report contract drift
- Keep contracts aligned with service-local semantics and workflow expectations
Read Before Editing
AGENTS.md → global protocol
agent/codemap.yml → module constraints
.agents/skills/backend-engineering/SKILL.md → backend quality kernel
services/<name>/model.yaml → commands/events/queries source context
platform/model/workflows/** → workflow-driven protocol context
docs/contracts/** → existing contract documentation
Writable Directories
| Directory | Scope |
|---|---|
packages/contracts/** |
Source contract types |
docs/contracts/** |
Contract documentation |
verification/contract/** |
Contract validation tests |
Forbidden Directories
| Directory | Reason |
|---|---|
packages/sdk/** |
Generated from contracts (read-only) |
docs/generated/** |
Generated (read-only) |
services/** |
Owned by service-agent |
servers/** |
Owned by server-agent |
workers/** |
Owned by worker-agent |
infra/** |
Owned by platform-ops-agent |
packages/**/adapters/** |
Concrete adapter implementations |
Gate Candidates
Select gates from agent/manifests/gate-matrix.yml based on changed paths, risk, and evidence level. Common contract signals include:
| Gate | Command |
|---|---|
| Type generation | moon run repo:typegen |
| Contract drift check | git diff --exit-code packages/contracts/generated/ |
| Typecheck | just typecheck |
| Boundary check | just boundary-check |
Hard Rules
Workflow skills, including backend-engineering, may guide process; this skill's ownership boundaries still apply.
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.
- 8d ago First seen · 96 lines · 72 tokens per session scan A a0a485271aa2
contract-agent is a skill published in the GitHub repository openclosed-org/axum-harness (49 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 661 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-30.
Other skills, from other repositories
architecture-paradigm-microservices
Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.
microservices-expert
Expert-level microservices architecture, patterns, service mesh, and distributed systems. Use when the user mentions distributed systems, service mesh, or architecture, or when the task involves Microservices Principles, Architecture Patterns, Communication, or Data Management.
microservices-patterns
Generate and review microservices code using patterns from Chris Richardson's "Microservices Patterns." Use this skill whenever the user asks about microservices architecture, wants to generate service code, design distributed systems, review microservices code, implement sagas, set up CQRS, configure API gateways…
distributed-feasibility-checker
Evaluate whether a system should adopt distributed architecture by systematically checking against the 8 Fallacies of Distributed Computing and assessing team/operational readiness. Use this skill whenever the user is considering microservices, debating monolith vs distributed, hearing "let's use microservices,"…
distributed-systems
Distributed systems patterns for locking, resilience, idempotency, and rate limiting. Use when implementing distributed locks, circuit breakers, retry policies, idempotency keys, token bucket rate limiters, or fault tolerance patterns.
Contract Testing with Pact
Consumer-driven contract testing skill using Pact, covering consumer tests, provider verification, Pact Broker integration, and CI/CD workflows.