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 hoavdc/CodexKit --skill codexkit-policy-document-writergit 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-policy-document-writer)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-policy-document-writer"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-policy-document-writer/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/hoavdc/codexkit/codexkit-policy-document-writer"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-policy-document-writer.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.00059 | $0.01457 |
| Opus 5.5 | $0.00024 | $0.00583 |
| Sonnet 5.5 | $0.00012 | $0.00291 |
| Haiku 4.5 | $0.00006 | $0.00146 |
Grade A, and why
codexkit-policy-document-writer 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 1mo 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Policy Document Writer
When to Use
- When creating a new corporate policy or procedure
- When formalizing informal processes into official SOPs
- When audit findings require documented policies
- When regulatory requirements demand written procedures
Procedure
Step 1 — Document Control Header
| Field | Value |
|---|---|
| Document ID | POL-[Department]-[NNN] |
| Title | [Clear, specific title] |
| Version | 1.0 |
| Effective Date | [Date] |
| Review Date | [12 months from effective] |
| Owner | [Role/Name] |
| Approver | [Role/Name] |
| Classification | Internal / Confidential / Public |
Step 2 — Purpose & Scope
Purpose: One paragraph explaining:
- WHY this policy exists
- WHAT problem it addresses
- WHAT compliance requirement it satisfies (if any)
Scope:
- Who this applies to (roles, departments, locations)
- What it covers (and explicitly what it does NOT cover)
- When it takes effect
Step 3 — Definitions
Define key terms to avoid ambiguity:
| Term | Definition |
|---|---|
| PII | Personally Identifiable Information — any data that can identify an individual |
| Data Controller | Entity that determines purposes and means of processing personal data |
Step 4 — Roles & Responsibilities
| Role | Responsibilities |
|---|---|
| Policy Owner | Maintains, reviews, updates the policy |
| Department Heads | Ensures team compliance, reports violations |
| All Employees | Reads, understands, follows the policy |
| Compliance Team | Monitors adherence, conducts audits |
Step 5 — Policy Statements
Write clear, enforceable statements:
Good:
All employees must complete security awareness training within 30 days of hire and annually thereafter.
Bad:
Employees should try to complete training when possible.
Rules for policy statements:
- Use "must" for requirements, "should" for recommendations
- Be specific about timeframes, quantities, and thresholds
- Include consequences for non-compliance
- Reference related policies by ID
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.
- 1mo ago First seen · 193 lines · 59 tokens per session scan A 169f3244cdb8
codexkit-policy-document-writer is a skill published in the GitHub repository hoavdc/CodexKit (26 stars, last pushed 12d ago), licensed MIT. It adds 59 tokens to every session and 1,457 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
architecting-security
A security-architecture guide for modeling threats and designing identity, access, privacy, and compliance controls. It covers approaches such as STRIDE, zero trust, single sign-on, multi-factor authentication, and GDPR-related privacy work.
bionic-safety-net
Unified survival infrastructure: health, finance, legal safety, circuit breakers, and structural protection against all ruin classes. The last line of defense.
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
lex-ignvvcio254
Centralized 'Truth Engine' for cross-jurisdictional legal context (US, EU, CA) and contract scaffolding.
reducing-aigc-detection
A rewriting workflow for lowering the likelihood that academic writing is labelled as AI-generated by detection services, while keeping formatting and footnotes.
aviation-inspector
Use when a task needs the judgment of an Aviation Inspector — determining whether an air carrier's fleet is in compliance with an Airworthiness Directive across a maintenance-records sample, deciding where the FAA's compliance-and-enforcement ladder places a finding (compliance action vs. Letter of Correction vs.…