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-audit-readiness-checkergit 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-audit-readiness-checker)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-audit-readiness-checker"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-audit-readiness-checker/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-audit-readiness-checker"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-audit-readiness-checker.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.00075 | $0.01273 |
| Opus 5.5 | $0.00030 | $0.00509 |
| Sonnet 5.5 | $0.00015 | $0.00255 |
| Haiku 4.5 | $0.00007 | $0.00127 |
Grade A, and why
codexkit-audit-readiness-checker 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Readiness Checker
When to Use
- 60–90 days before a scheduled external audit
- When preparing for SOX compliance for the first time
- After prior audit findings need remediation verification
- When internal audit wants a pre-flight check
Procedure
Step 1 — Map Assertions to Accounts
For each material account balance, map the relevant audit assertions:
| Assertion | What It Tests |
|---|---|
| Existence/Occurrence | Did the transaction/asset actually happen/exist? |
| Completeness | Are all transactions recorded? |
| Valuation/Accuracy | Are amounts recorded correctly? |
| Rights & Obligations | Does the entity own/owe the amounts? |
| Presentation & Disclosure | Is it properly classified and disclosed? |
| Cut-off | Are transactions in the correct period? |
Step 2 — Check Evidence Completeness
For each assertion per account, verify supporting evidence:
- Source documents (invoices, contracts, bank statements)
- Reconciliations (bank, intercompany, sub-ledger to GL)
- Approvals and authorization records
- Third-party confirmations
- Management representations and estimates documentation
Step 3 — Score Readiness
| Score | Criteria |
|---|---|
| 🟢 Green | All evidence available, reconciled, no open items |
| 🟡 Amber | Evidence partially available, minor gaps, reconciliation in progress |
| 🔴 Red | Missing evidence, unreconciled, prior audit finding unresolved |
Step 4 — Generate Remediation Plan
For each 🟡 and 🔴 item:
- Describe the gap
- Assign an owner
- Set a deadline (must be before audit fieldwork)
- Define the evidence deliverable
Inputs
| Input | Required | Format |
|---|---|---|
| Trial balance | Yes | Account list with balances |
| Prior audit findings | Recommended | Management letter or audit report |
| Audit timeline | Yes | Fieldwork start date |
| Supporting schedules | Recommended | Reconciliations, roll-forwards |
Output
## Audit Readiness Scorecard — [Entity] — [Audit Period]
### Overall Score: 🟡 AMBER (72% ready — 12 weeks to fieldwork)
### By Account Area
| Account | Assertion | Evidence | Status | Gap | Owner | Deadline |
|---------|-----------|----------|--------|-----|-------|----------|
| Cash | Existence | Bank confirmations | 🟢 | — | — | — |
| Cash | Completeness | Bank reconciliation | 🟢 | — | — | — |
| AR | Existence | Confirmations | 🟡 | 3 confirmations pending | AR Lead | Week 8 |
| AR | Valuation | Aging + allowance | 🔴 | Allowance model not updated | Controller | Week 6 |
| Revenue | Cut-off | Shipping docs | 🟢 | — | — | — |
| PP&E | Existence | Physical count | 🔴 | Count not scheduled | Ops Mgr | Week 4 |
### Prior Findings Status
| Finding | Year | Status | Remediation |
|---------|------|--------|-------------|
| Inventory count procedures | 2024 | 🟡 In progress | New SOP drafted, testing pending |
| AR confirmation process | 2024 | 🟢 Resolved | Automated via NetSuite |
### Remediation Timeline
| Week | Action | Owner |
|------|--------|-------|
| Week 4 | Schedule PP&E physical count | Ops Manager |
| Week 6 | Update AR allowance model | Controller |
| Week 8 | Complete AR confirmations | AR Lead |
| Week 10 | Final reconciliation review | CFO |
| Week 12 | Audit fieldwork begins | — |
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 · 146 lines · 75 tokens per session scan A e8212175e60c
codexkit-audit-readiness-checker is a skill published in the GitHub repository hoavdc/CodexKit (26 stars, last pushed 12d ago), licensed MIT. It adds 75 tokens to every session and 1,273 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
bionic-safety-net
Unified survival infrastructure: health, finance, legal safety, circuit breakers, and structural protection against all ruin classes. The last line of defense.
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.
bartender
Use when a task needs the judgment of a Bartender — reconciling actual pour cost against theoretical liquor cost by drink category, deciding whether and how to cut off a guest, pricing a drink menu across well/call/premium tiers, closing out a till and comp log at shift end, or sequencing bar-top service against a…
bill-account-collector
Use when a task needs the judgment of a bill and account collector — prioritizing a delinquent-account portfolio by recovery likelihood, structuring a payment plan against a debtor's stated ability to pay, drafting an FDCPA/Reg F-compliant collection communication, handling a cease-and-desist or debt dispute, or…
einvoicing-zatca-peppol-compliance
Implement government electronic invoicing standards including UBL 2.1 XML, Peppol BIS Billing 3.0, and Saudi ZATCA (FATOORA Phase 2) compliance. Generate cryptographic invoice hashes (SHA-256), ECDSA secp256k1 digital signatures, TLV-encoded Base64 QR codes, and clearance/reporting API integrations. Trigger when…
rise-licensing
You are an SAP licensing and commercial strategy expert. RISE with SAP is a complex bundled offering. Your job is to prevent clients from committing to contract terms they do not understand, missing cost optimization levers, or choosing infrastructure options that will constrain them for five or more years.