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 agentmods add skills/usathyan/epistract/contractsnpx skills add usathyan/epistract --skill contractsgit clone --depth 1 https://github.com/usathyan/epistractWrote 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/usathyan/epistract/contracts)<a href="https://agentmods.dev/skills/usathyan/epistract/contracts"><img src="https://agentmods.dev/badge/skills/usathyan/epistract/contracts.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 | $0.00000 | $0.00291 |
| Opus 5 | $0.00000 | $0.00146 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
contracts 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 5d 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.
What it actually says
Contract Analysis Domain
Extract structured knowledge from event contracts, vendor agreements, and service-level agreements.
Entity Types
| Type | Description |
|---|---|
| PARTY | Organization or individual signatory |
| CONTRACT | Formal agreement between parties |
| OBLIGATION | Required action or compliance requirement |
| DEADLINE | Date or time constraint |
| COST | Monetary amount or payment term |
| VENUE | Physical location |
| SERVICE | Service provided under contract |
| INSURANCE | Insurance requirement or coverage |
| PENALTY | Consequence for breach |
Relation Types
| Type | Description |
|---|---|
| OBLIGATED_TO | Party must fulfill obligation |
| HAS_DEADLINE | Obligation has a deadline |
| COSTS | Service has associated cost |
| SIGNED_BY | Contract signed by party |
| PROVIDES_SERVICE | Party provides service |
| HELD_AT | Event at venue |
| REQUIRES_INSURANCE | Contract requires insurance |
| CROSS_REFERENCES | Contract references another |
| PENALIZES | Breach triggers penalty |
Extraction Guidelines
- Every obligation must link to a responsible party and a deadline if specified
- Costs should be extracted with currency and payment terms
- Cross-contract references are high-value -- they reveal dependencies between vendors
- Insurance requirements should capture coverage type and minimum amounts
- Penalties should link to the specific obligation they enforce
What ships with it
6 files 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.
- 5d ago First seen · 40 lines · 0 tokens per session scan A 64041d55909c
contracts is a skill published in the GitHub repository usathyan/epistract (8 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 291 tokens. 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
specification-writing
Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
steward-prep-delivery
Steward-assisted prep for filing issues and PRs — environment capture, template selection, duplicate detection, delivery-policy compliance check.
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…