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 commands/brainbytes-dev/everything-claude-finance/audit-checklistgit clone --depth 1 https://github.com/brainbytes-dev/everything-claude-financeWrote 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/commands/brainbytes-dev/everything-claude-finance/audit-checklist)<a href="https://agentmods.dev/commands/brainbytes-dev/everything-claude-finance/audit-checklist"><img src="https://agentmods.dev/badge/commands/brainbytes-dev/everything-claude-finance/audit-checklist.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.00009 | $0.01304 |
| Opus 5 | $0.00005 | $0.00652 |
| Sonnet 5 | $0.00002 | $0.00261 |
| Haiku 4.5 | $0.00001 | $0.00130 |
Grade A, and why
audit-checklist 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit-checklist — Audit Preparation Checklist
What This Command Does
Generates a comprehensive audit preparation checklist tailored to the entity, audit area, and applicable standards. Covers documentation requirements, testing procedures, evidence gathering, and common findings to watch for. Tracks completion status and flags high-risk areas requiring additional scrutiny.
When to Use
- Preparing for external audit (year-end or interim)
- Internal audit planning and execution
- First-year audit preparation
- Audit readiness assessment before auditors arrive
- SOX compliance testing preparation
- Remediation tracking for prior-year findings
How It Works
- Risk Assessment: Identifies high-risk areas based on entity type, industry, and prior findings
- Checklist Generation: Creates area-specific procedures aligned with ISA/PCAOB standards
- Documentation Map: Lists required PBC (prepared by client) documents per area
- Testing Procedures: Defines sample sizes, selection methods, and assertion coverage
- Completion Tracking: Provides status tracking with reviewer sign-off fields
- Issues Log: Templates for documenting findings and management responses
Example Usage
Input:
/audit-checklist entity:"Nordic Pharma AS" area:revenue standard:IFRS materiality:500000
Output:
# Audit Preparation Checklist — Nordic Pharma AS
## Area: Revenue | Standard: IFRS 15 | Materiality: EUR 500K
## Audit Period: FY2025 | Prepared: 2026-03-14
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Risk Assessment — Revenue
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
| Risk Factor | Level | Rationale |
|--------------------------------|--------|---------------------------------|
| Revenue recognition complexity | High | Multiple performance obligations|
| Contract modifications | Medium | Frequent amendment patterns |
| Variable consideration | High | Rebates, returns, milestones |
| Cut-off risk | Medium | Year-end shipment timing |
| Fraud risk (ISA 240) | Present| Presumed risk per standards |
Planned approach: Combined (controls + substantive testing)
Sample size: 25 transactions (statistical, MUS method)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## PBC Document Checklist
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
| # | Document | Status | Due Date |
|---|---------------------------------------|--------|------------|
| 1 | Revenue recognition policy memo | ⬜ | 2026-02-28 |
| 2 | Complete contract listing (top 50) | ⬜ | 2026-02-28 |
| 3 | Revenue by product line / geography | ⬜ | 2026-03-05 |
| 4 | Credit note / returns summary | ⬜ | 2026-03-05 |
| 5 | Rebate and discount schedule | ⬜ | 2026-03-05 |
| 6 | Deferred revenue rollforward | ⬜ | 2026-03-10 |
| 7 | Bill-and-hold arrangement details | ⬜ | 2026-03-10 |
| 8 | Related party sales listing | ⬜ | 2026-03-10 |
| 9 | Revenue cut-off testing schedule | ⬜ | 2026-03-15 |
|10 | Management representation letter | ⬜ | 2026-03-30 |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Testing Procedures
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
### IFRS 15 Five-Step Model Testing
| Step | Procedure | Status |
|-------------------------------|--------------------------------|--------|
| 1. Identify contract | Verify signed agreements exist | ⬜ |
| 2. Identify perf. obligations | Test allocation of bundled deals| ⬜ |
| 3. Determine transaction price| Verify variable consideration | ⬜ |
| 4. Allocate to perf. oblig. | Test standalone selling prices | ⬜ |
| 5. Recognize revenue | Test timing — point vs. over time| ⬜ |
### Substantive Procedures
| # | Procedure | Assertion | Status |
|---|---------------------------------------|-------------|--------|
| 1 | Sales to cash receipts tracing (25) | Occurrence | ⬜ |
| 2 | Cash receipts to sales (25) | Completeness| ⬜ |
| 3 | Year-end cut-off testing (±5 days) | Cut-off | ⬜ |
| 4 | Analytical review — monthly trends | Reasonableness| ⬜ |
| 5 | Related party transaction review | Valuation | ⬜ |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## Common Findings Watchlist
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚠ Pharma industry: Watch for channel-stuffing patterns in Q4
⚠ Milestone-based contracts: Verify constraint on variable consideration
⚠ Rebate accruals: Test historical accuracy of estimates
⚠ Bill-and-hold: Verify all criteria under IFRS 15.B79-B82
### Issues Log Template
| # | Finding | Severity | Ref | Mgmt Response | Status |
|---|---------|----------|-----|---------------|--------|
| | | | | | |
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 · 130 lines · 9 tokens per session scan A b996c82179ab
audit-checklist is a command published in the GitHub repository brainbytes-dev/everything-claude-finance (5 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 1,304 once invoked, about $0.0000 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 commands, from other repositories
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
scan
Scan AWS account for cost optimization.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…