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/hoavdc/codexkit/codexkit-contract-risk-reviewnpx skills add hoavdc/CodexKit --skill codexkit-contract-risk-reviewgit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-contract-risk-review)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-contract-risk-review"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-contract-risk-review.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.00083 | $0.00690 |
| Opus 5 | $0.00042 | $0.00345 |
| Sonnet 5 | $0.00017 | $0.00138 |
| Haiku 4.5 | $0.00008 | $0.00069 |
Grade A, and why
codexkit-contract-risk-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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contract Risk Review
Purpose
Surface business and contractual risk quickly so a human reviewer can negotiate or escalate intelligently.
When to use
- A contract needs first-pass risk review before legal or procurement sign-off.
- A business owner wants obligations, liabilities, and red flags summarized.
- A negotiation needs fallback positions and open questions.
When not to use
- The user needs formal legal advice for a specific jurisdiction.
- The task is drafting litigation arguments or dispute strategy.
Inputs
- contract text or key clauses
- deal context, commercial goals, and fallback positions
- known red lines, approval thresholds, and data or security concerns
Procedure
- Classify the agreement type and commercial stakes.
- Review key clause families: scope, fees, term, liability, IP, confidentiality, data, termination, and dispute language.
- Extract obligations, asymmetries, unusual exposure, and missing protections.
- Rate issues by business impact and negotiation urgency.
- Suggest fallback language or negotiation positions without pretending to replace counsel.
- Call out where legal review is mandatory.
Output
- executive contract summary
- clause-by-clause risk table
- top red flags and why they matter
- fallback positions or negotiation notes
- unresolved questions for counsel or stakeholders
Definition of done
- A business owner can see the highest-risk clauses quickly.
- Missing protections and unclear obligations are explicit.
- The output states where human legal review is still required.
Examples
- "Review this vendor MSA and flag the clauses we should negotiate before signing."
- "Summarize our obligations and main risks in this customer SOW."
Quality Criteria
- Every finding is tied to a specific evidence source (log, test, metric)
- Pass/fail criteria are binary and measurable — no subjective judgments
- Severity levels are assigned with clear thresholds
- Remediation steps are provided for all critical and high findings
What ships with it
4 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.
- 4d ago First seen · 84 lines · 83 tokens per session scan A 96833e8ee782
codexkit-contract-risk-review is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 83 tokens to every session and 690 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
reducing-aigc-detection
Systematically reduce AIGC detection rates in academic papers (Chinese/English). Analyzes detection reports, identifies high-impact sections, applies multi-layer rewriting strategies preserving formatting/footnotes, and verifies results. Supports 维普/知网/Turnitin platforms.
architecting-security
安全架构与治理：威胁建模 (STRIDE/PASTA/LINDDUN)、零信任身份架构、IAM/SSO/MFA/PAM、合规框架 (SOC2/PCI/HIPAA/GDPR)、DLP、隐私工程、安全控制设计。Use when designing security architecture, threat modeling new systems, implementing zero-trust identity, designing IAM/SSO/PAM, building compliance evidence chains, or planning privacy-by-design.
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…
detecting-and-responding
蓝队与紫队工程：检测规则编写、SIEM/EDR 调优、事件响应、数字取证、威胁狩猎、ATT&CK 映射、紫队演练闭环。Use when writing Sigma/YARA detection rules, tuning SIEM noise, responding to security incidents, conducting forensic analysis, hunting threats, or running purple team exercises.
securing-cloud-and-supply-chain
云原生与软件供应链安全防御。容器/K8s 加固、Service Mesh、CI/CD 安全、SLSA/SBOM/Sigstore、云 IAM、Secrets 管理、IaC 安全。Use when hardening Kubernetes clusters, auditing CI/CD pipelines, implementing supply chain security, managing cloud IAM, or reviewing IaC code.
verification-loop
Evidence-before-assertions workflow. Use before claiming work is done, before release, and after any behavior change in scripts/skills/MCP.