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-drafternpx skills add hoavdc/CodexKit --skill codexkit-contract-draftergit clone --depth 1 https://github.com/hoavdc/CodexKitWhat 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.00071 | $0.00978 |
| Opus 5 | $0.00036 | $0.00489 |
| Sonnet 5 | $0.00014 | $0.00196 |
| Haiku 4.5 | $0.00007 | $0.00098 |
Grade A, and why
codexkit-contract-drafter 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 2d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contract Drafter
Purpose
Generate well-structured contracts using a clause library approach — producing balanced terms that protect both parties while reflecting business intent.
When to use
- creating a new NDA, service agreement, or vendor contract from scratch
- drafting a partnership or licensing agreement
- creating an employment contract or consulting agreement
- when no internal template exists for the contract type needed
When not to use
- reviewing or redlining an existing contract (use contract-risk-review)
- high-value M&A transactions (requires specialized legal counsel)
- jurisdictions with specific regulatory requirements without local counsel input
Inputs
- contract type (NDA / Service Agreement / Vendor Agreement / Employment / License / Partnership)
- parties involved (names, roles, jurisdictions)
- key commercial terms (scope, duration, pricing, payment terms)
- specific requirements or non-standard terms
- governing law preference
- risk tolerance (conservative / balanced / aggressive)
Procedure
- Select contract template structure based on type:
- Recitals (background and purpose)
- Definitions section
- Core commercial terms
- Protective clauses
- Standard boilerplate
- Draft core clauses — each with balanced terms:
- Scope of Work / Services: clear deliverables + acceptance criteria
- Payment Terms: milestones, net days, late payment interest
- Term and Renewal: fixed term, auto-renewal notice period
- Termination: for cause + for convenience, notice period, wind-down
- Draft protective clauses:
- IP Ownership: background IP protected, work product assignment
- Confidentiality: duration, permitted disclosures, return of info
- Liability Cap: mutual cap at contract value (or last 12 months fees)
- Indemnification: mutual, limited to direct damages
- Force Majeure: modern clause including pandemic, cyber attack
- Dispute Resolution: escalation path → mediation → arbitration/court
- Add boilerplate:
- Entire Agreement, Severability, Waiver, Assignment, Notices
- Risk-calibrate based on tolerance:
- Conservative: more protections, lower caps, stricter terms
- Balanced: mutual obligations, reasonable caps
- Aggressive: fewer restrictions, higher risk acceptance
- Flag missing clauses that the other party may request.
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.
- 2d ago First seen · 110 lines · 71 tokens per session scan A 349fabee4b8a
codexkit-contract-drafter is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 978 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.
analyzing-changes
Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.