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 fergupa/claude_plugins --skill close-managementgit clone --depth 1 https://github.com/fergupa/claude_pluginsWrote 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/fergupa/claude_plugins/close-management)<a href="https://agentmods.dev/skills/fergupa/claude_plugins/close-management"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/close-management/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/fergupa/claude_plugins/close-management"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/close-management.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.00040 | $0.02137 |
| Opus 5.5 | $0.00016 | $0.00855 |
| Sonnet 5.5 | $0.00008 | $0.00427 |
| Haiku 4.5 | $0.00004 | $0.00214 |
Grade A, and why
close-management 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.
This is a copy
97% identical to close-management — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close Management
Important: This skill assists with close management workflows but does not provide financial advice. All close activities should be reviewed by qualified financial professionals.
Month-end close checklist, task sequencing and dependencies, status tracking, and common close activities organized by day.
Month-End Close Checklist
Pre-Close (Last 2-3 Business Days of the Month)
- Send close calendar and deadline reminders to all contributors
- Confirm cut-off procedures with AP, AR, payroll, and treasury
- Verify all sub-systems are processing normally (ERP, payroll, banking)
- Complete preliminary bank reconciliation (all but last-day activity)
- Review open purchase orders for potential accrual needs
- Confirm payroll processing schedule aligns with close timeline
- Collect information for any known unusual transactions
Close Day 1 (T+1: First Business Day After Month-End)
- Confirm all sub-ledger modules have completed period-end processing
- Run AP accruals for goods/services received but not invoiced
- Post payroll entries and payroll accrual (if pay period straddles month-end)
- Record cash receipts and disbursements through month-end
- Post intercompany transactions and confirm with counterparties
- Complete bank reconciliation with final bank statement
- Run fixed asset depreciation
- Post prepaid expense amortization
Close Day 2 (T+2)
- Complete revenue recognition entries and deferred revenue adjustments
- Post all remaining accrual journal entries
- Complete AR subledger reconciliation
- Complete AP subledger reconciliation
- Record inventory adjustments (if applicable)
- Post FX revaluation entries for foreign currency balances
- Begin balance sheet account reconciliations
Close Day 3 (T+3)
- Complete all balance sheet reconciliations
- Post any adjusting journal entries identified during reconciliation
- Complete intercompany reconciliation and elimination entries
- Run preliminary trial balance and income statement
- Perform preliminary flux analysis on income statement
- Investigate and resolve material variances
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 · 221 lines · 40 tokens per session scan A 7901f839cba3
close-management is a skill published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,137 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to close-management, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
weekly-update
OpenDesign's weekly metrics standup: this week's numbers, the one anomaly, and the single decision it forces. Built as a decision-grade data & finance deck for ops & growth team.
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.
closing-checklist
What's blocking close — maintain the closing checklist with status, critical path, and days to close. Self-updating: ingests new items from diligence findings and schedule builds, tracks status, surfaces what's blocking. Use when user says "closing checklist", "what's left to close", "checklist status", "add to the…
dd-checklist
Generate and track comprehensive due diligence checklists tailored to the target company's sector, deal type, and complexity. Covers all major workstreams with request lists, status tracking, and red flag escalation. Use when kicking off diligence, organizing a data room review, or tracking outstanding items. Triggers…
bo-vendor-review
A framework for comparing supplier proposals and renewal choices using costs, service terms, operational fit, contracts, and business-continuity risks. It treats one-time, recurring, and usage-based charges separately when comparing prices.
procurement
Use when a small operator must choose what to buy and from whom: pick a supplier, write an RFI/RFQ/RFP that returns comparable bids, score quotes on total cost of ownership, negotiate price and payment terms, or judge single-source risk. NOT redlining the purchase agreement (that is contracts), NOT the price you…