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 skills/hoavdc/codexkit/codexkit-finance-close-coordinatornpx skills add hoavdc/CodexKit --skill codexkit-finance-close-coordinatorgit clone --depth 1 https://github.com/hoavdc/CodexKitWhat 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.00062 | $0.00605 |
| Opus 5 | $0.00031 | $0.00302 |
| Sonnet 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 3d 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.
- 3d 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 (21 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 605 once invoked, about $0.0003 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
agent-agentic-payments
Agent skill for agentic-payments - invoke with $agent-agentic-payments.
agent-payments
Agent skill for payments - invoke with $agent-payments.
stock-analyzer
A comprehensive stock deep analysis tool that combines real-time quotes, fundamental metrics, technical indicators, and growth analysis into a single professional report. Supports A-share, US stocks, HK stocks. Generates detailed investment recommendations with risk assessment and actionable trading strategies.
stock-announcements
Skill "stock-announcements" from netease-youdao/LobsterAI, covering stock announcement fetcher, 真实数据保证, dependencies, when to use this skill and usage.
stock-explorer
A Yahoo Finance (yfinance) powered financial analysis tool. Get real-time quotes, generate technical indicator reports (RSI/MACD/Bollinger/VWAP/ATR), summarize fundamentals, and run a one-shot report that outputs a text summary.
bionic-safety-net
Unified survival infrastructure: health, finance, legal safety, circuit breakers, and structural protection against all ruin classes. The last line of defense.