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 coreyhaines31/makerskills --skill company-cfogit clone --depth 1 https://github.com/coreyhaines31/makerskillsWrote 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/coreyhaines31/makerskills/company-cfo)<a href="https://agentmods.dev/skills/coreyhaines31/makerskills/company-cfo"><img src="https://agentmods.dev/badge/skills/coreyhaines31/makerskills/company-cfo/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/coreyhaines31/makerskills/company-cfo"><img src="https://agentmods.dev/badge/skills/coreyhaines31/makerskills/company-cfo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 163 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 178 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 164 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 121 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00202 | $0.03658 |
| Opus 5 | $0.00101 | $0.01829 |
| Sonnet 5 | $0.00040 | $0.00732 |
| Haiku 4.5 | $0.00020 | $0.00366 |
Grade A, and why
company-cfo 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 11d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/company-cfo — Monthly company CFO workflow
The standing analysis leadership uses to make distribution / cuts / hiring / runway decisions. Primary cadence is monthly (run on the 1st for the closed prior month). Weekly and scenario modes cover the in-between.
Anonymized team-scope sibling to personal-cfo (households). Same discipline (transaction-sum EOM, categorization traps, scenario modeling) applied to company books.
Step 0 — Load company config + prior run
Before starting work, read these in order:
${COMPANY_CFO_ROOT:-$HOME/code/company-cfo}/CLAUDE.md— your company's specific methodology, data source map, categorization rules, distribution mechanics. This is the source of truth for HOW your company computes things. Don't invent your own methodology.- The most recent report in
${COMPANY_CFO_ROOT}/reports/monthly/— last month's snapshot. Tells you what leadership decided + what was open. - The most recent
*-followup.mdin that folder (if one exists) — supplementary decisions, scenario analysis. - Any relevant memory notes in
~/.claude/memory/— running context: known anomalies, leadership constraints, current churn state. git log --oneline -10in${COMPANY_CFO_ROOT}— what's shipped since the last run.
If the COMPANY_CFO_ROOT dir doesn't exist yet: first-run walkthrough asks the user to mkdir it, seed a CLAUDE.md from references/company-config-template.md, and set the env var.
Step 1 — Parse mode
| Invocation | Mode | Cadence |
|---|---|---|
/company-cfo monthly (default) |
monthly | Once per month on the 1st for the closed prior month |
/company-cfo weekly |
weekly | Thin cash pulse — current cash + next 2 weeks of expected flows |
/company-cfo scenario <question> |
scenario | Ad-hoc modeling in the projector |
/company-cfo pickup |
pickup | Resume where the prior run left off (checks git log + last report + open items) |
Below sections walk through monthly in detail. Weekly + scenario are summarized at the end.
What ships with it
6 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.
- 11d ago First seen · 250 lines · 202 tokens per session scan A 579aab4e80cf
company-cfo is a skill published in the GitHub repository coreyhaines31/makerskills (803 stars, last pushed 6d ago), licensed MIT. It adds 202 tokens to every session and 3,658 once invoked, about $0.0010 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
converge
Append-only gap closure and the cadence engine for research theses. Evaluates artifact CURRENT state (never git history, never task checkboxes) against current pins and wrongif falsifiers, then appends a Convergence section to tasks.md re-proposing the gaps. A clean run leaves tasks.md byte-identical. Deterministic…
implement
Execute research tasks — checklist soft gate, phase dispatch with explicit thesisdir, budget enforcement (halt + approval card on overrun), skillpin recording (versionhash content-hashed per skill directory), [x] written on completion.
audit-support
Gets the books audit-ready: builds the PBC (prepared-by-client) list by area, drafts walkthrough narratives for key cycles (revenue, purchases, payroll), matches auditor samples to support, prepares tie-out schedules, tracks open items with owners and due dates, and drafts responses to findings. Use when the user says…
financial-statements
Builds a full statement set — P&L, balance sheet, and indirect cash flow — from a trial balance or transaction export, mapping accounts to a standard chart and proving every tie-out in code. Use when the user says 'build a P&L from this trial balance', 'turn this export into financials', 'I need a balance sheet for…
invoice-chase
Runs collections on late invoices: builds an aging ladder (current/30/60/90+), assigns each invoice a rung on an escalation sequence with ready-to-send emails — friendly nudge, firm reminder with late-fee mention, final notice — plus a phone script, tone rules that preserve the relationship, a chase log, and…
plan-payroll
Plans payroll cash: true loaded cost per hire (gross plus employer taxes, benefits, tools), a payroll calendar with cutoffs and cash-out dates, a scenario table for new hire vs raise vs contractor-vs-employee, and a payroll-to-revenue check against rough industry bands. Use when the user asks "can I afford to hire"…