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 event4u-app/agent-config --skill contract-reviewgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/contract-review)<a href="https://agentmods.dev/skills/event4u-app/agent-config/contract-review"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/contract-review/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/event4u-app/agent-config/contract-review"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/contract-review.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.00047 | $0.02063 |
| Opus 5 | $0.00023 | $0.01032 |
| Sonnet 5 | $0.00009 | $0.00413 |
| Haiku 4.5 | $0.00005 | $0.00206 |
Grade A, and why
contract-review 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
contract-review
When to use
- A contract draft (MSA / SOW / vendor / licence / partner agreement) needs a position-aware, clause-by-clause review — the user states their party role and the review adjusts to what their side should fear.
- An existing contract is being negotiated and each load-bearing clause needs a GREEN / YELLOW / RED severity call plus a specific redline suggestion (not an edit).
- A non-lawyer needs the analysis that prepares the attorney conversation: what each clause binds, where the risk concentrates, what to ask for.
Do NOT use to issue a legal opinion (the licensed attorney decides — see legal-safety-floor), for the non-lawyer cognition layer that precedes a structured review (route to contracts-cognition), or for DPA / data-processing review (route to dpa-review).
Procedure
Step 0: Fix the party role and the jurisdiction
- The user states their party role:
buyer/seller/vendor/licensee/licensor(or the contract's own term). The review is asymmetric — a cap that protects the seller exposes the buyer. If the role is missing, STOP and ask once. Do not infer from prose. - Read the governing-law clause. If the contract is governed by a jurisdiction outside EU/DE scope, REFUSE the review: "This is governed by <jurisdiction> — outside this pack's EU/DE scope. Consult licensed local counsel." Never a stale guess for an out-of-scope jurisdiction.
- Tag the output with
Jurisdiction: EUorJurisdiction: DE— the one you reasoned under.
Step 1: Establish the position profile
Read thresholds and acceptable positions from the legal-practice-profile (sibling skill). The skill ships no default legal positions — caps, notice windows, indemnity shapes, and acceptable-risk bands are the profile's, not the agent's.
Until the profile is configured, emit explicit [configure] placeholders (e.g. "indemnity cap acceptable band: [configure]") and say plainly that no position is being asserted.
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.
- 9d ago First seen · 126 lines · 47 tokens per session scan A 60ef3dcba6c2
contract-review is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,063 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
telnyx-email-suppressions-curl
Manage email suppressions (blocks), import and export suppression lists, and manage unsubscribe groups. Use for deliverability compliance and bounce handling.
healthcare-providers-verify
Validates practitioner credentials and license status against the NPI registry. Cross-references specialties, credentials, and practice addresses against official records. Returns Verified / Partially Verified / Unverified / Flagged per practitioner with mismatch details and source URLs. Triggers: "verify these…
python-packaging-license-finder
Use this skill to deterministically find license information for Python packages by checking PyPI metadata first, then falling back to Git repository LICENSE files using shallow cloning.
patent-review
Multi-round cyclic rigorous review of Chinese patent technical disclosure documents. Supports multi-dimension review (data flow closure, terminology consistency, state transition, formula completeness, error code routing, text-diagram consistency), round-by-round convergence, and optional auto-fix (default off, severe…
template-redacted-report
Redacted release-report exemplar for classification ceilings, source protection, source-safe ledgers, reviewer gates, and mosaic-risk checks.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.