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-finance-close-coordinatorgit 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-finance-close-coordinator)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-finance-close-coordinator"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-finance-close-coordinator/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-finance-close-coordinator"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-finance-close-coordinator.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.00062 | $0.00605 |
| Opus 5.5 | $0.00025 | $0.00242 |
| Sonnet 5.5 | $0.00012 | $0.00121 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
codexkit-finance-close-coordinator 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finance Close Coordinator
Purpose
Keep close operations moving with a short, decision-ready issue view.
When to use
- close has many open issues and no clean tracker
- controllers or FP&A need one summary of blockers and owners
- evidence or reconciliations are arriving in fragments
When not to use
- the user needs accounting analysis under IFRS, GAAP, or tax rules
- the task is a variance story, not close coordination
Inputs
- close issue list or status notes
- reconciliations, evidence status, or owner updates
- period and escalation timing
Procedure
- Normalize each open issue into owner, status, risk, and due date.
- Separate evidence gaps from true close blockers.
- Flag items that could miss the period close.
- Group related issues under one line when possible.
- End with escalation items and next owner actions.
Output
- close blocker summary
- evidence and reconciliation gaps
- owner action list
- escalations for the period
Definition of done
- open close issues are visible in one read
- owners and deadlines are clear
- routine reminders are separated from real escalation risk
Examples
- "Summarize these close notes into blockers, gaps, and owners."
- "Turn this close tracker into a morning control pack."
Quality Criteria
- Steps are executable in sequence without external context
- Decision points have clear if/then branching
- Rollback or abort procedures are documented for risky steps
- Expected duration or time-per-step is estimated
Verification (4C)
| Check | Question |
|---|---|
| Correctness | Do the steps execute correctly in the order specified? |
| Completeness | Are decision points, error handling, and escalation paths all documented? |
| Context-fit | Could someone with the right access but no prior context complete this runbook? |
| Consequence | If Step N fails and the operator skips to Step N+1, what breaks? |
Edge Cases
- Steps require access the operator doesn't have — Document exact access requirements upfront. Include escalation contact for emergency access.
- Environment differs from documented state — Add a pre-flight check as Step 0 to verify prerequisites before starting.
- Runbook is triggered during off-hours — Document who to contact and which steps can be safely deferred to business hours.
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 · 82 lines · 62 tokens per session scan A b904735669a0
codexkit-finance-close-coordinator is a skill published in the GitHub repository hoavdc/CodexKit (26 stars, last pushed 11d ago), licensed MIT. It adds 62 tokens to every session and 605 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-08-30.
Other skills, from other repositories
fieldglass
Use when working with SAP Fieldglass — contingent workforce management, services procurement, Statement of Work (SOW), worker management lifecycle, rate card management, approval workflows, VMS reporting, or Fieldglass integration with S/4HANA.
community-market
A documented workflow for organising a community market, including permits, stallholder recruitment, publicity, site setup, event operations, and settlement. It records stall needs, attendance, fees, deposits, and sales information.
household-budget
A structured workflow and document library for managing a household budget, from reviewing income and spending through monthly tracking and agreed budget changes.
close-management
Manage the month-end close process with task sequencing, dependencies, and status tracking. Use when planning the close calendar, tracking close progress, identifying blockers, or sequencing close activities by day.
vendor-review
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
investment-report
Read when the user requests a synthesis, comparison, handoff, or durable report. Do not rerun unrelated analysis merely to fill a template.