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 davekilleen/Dex --skill close-statusgit clone --depth 1 https://github.com/davekilleen/DexWrote 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/davekilleen/dex/close-status)<a href="https://agentmods.dev/skills/davekilleen/dex/close-status"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/close-status/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/davekilleen/dex/close-status"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/close-status.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.00041 | $0.01096 |
| Opus 5.5 | $0.00016 | $0.00438 |
| Sonnet 5.5 | $0.00008 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
close-status 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Use when a finance or leadership user asks where a specified close period stands, what evidence supports completion, what is blocked, or which dependencies determine the sequence. Confirm the period, close deadline, and checklist scope before counting.
Do not use this skill to post journal entries, change the close checklist, certify completion, assign owners, or approve an accounting treatment. Not for budget-versus-actual explanation, forecasting, or audit sign-off.
Inputs and source discipline
- Identify the period, fiscal calendar/timezone, checklist version, and deadline. Use the
controller- or process-owner-approved authoritative checklist as the denominator source;
record its source, source date, date checked, and
as-ofdate. Never invent a deadline or silently substitute a remembered checklist. - For each checklist row, capture its stable label, required evidence, current evidence source, source date, date checked, named owner only if explicitly recorded, and confidence. Prefer system/close evidence and dated owner confirmation over meeting notes; use notes to locate evidence, not to override it. Preserve contradictory sources.
- Keep the checklist's scope and exclusions explicit. If the authoritative checklist is missing, partial, or stale, report the denominator as unknown rather than calculating a completion percentage.
Method
- Work read-only from the authoritative checklist and build one row per required item. Count an item complete only when its required evidence is present, dated, in scope, and reconciled; a statement that work is probably done is not completion evidence.
- Assign mutually exclusive states from evidence:
complete,in progress,blocked,not started, orunknown. Useblockedonly for a known impediment or dependency; useunknownwhen evidence is absent, stale, or contradictory; usenot startedonly when the source supports that state. Never convert missing evidence into not started. - Report completed rows as a counted numerator over the checklist denominator. Show a percentage
only when both are known and the counting rule is stated. Calculate days remaining only from a
supplied deadline and the stated
as-ofdate. - Build the dependency graph from explicit row dependencies, deadlines, and evidence. Call a chain the critical path only when the dependency evidence supports that claim; without durations or ordering evidence, report a dependency chain and say criticality is unknown.
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 Changed · +2 lines 5003e3fbbfe4
- 1mo ago First seen · 88 lines · 41 tokens per session scan A f0f05af3ae46
close-status is a skill published in the GitHub repository davekilleen/Dex (507 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,096 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
defi-protocol-templates
Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and flash loans. Use when building decentralized finance applications or smart contract protocols.
stripe-link-wallet
Agent wallet on the Stripe Link CLI (link-cli). Connect the wallet, then buy, purchase and pay for things on the user's behalf via approved spend requests, one-time-use cards, and 402 / Machine Payment Protocol (MPP) payments.
stripe-app-setup
Create and configure a Stripe restricted API key so the assistant can manage payments, subscriptions, and customers under its own scoped identity.
stock-analysis-lead
Orchestrate a US-stock investment analysis — classify sector archetype, fetch SEC filings, dispatch a tiered fan-out of six vertical equity-research agents (business model, earnings quality, balance sheet, management, industry, peer comparison) over a validated JSON findings contract, then synthesize a buy/hold/sell…
stock-business-review
Review a US-listed company's business model and revenue structure for an equity-research workup. Covers product/service mix, customer concentration, geographic exposure, industry position, revenue-growth decomposition (organic vs acquired vs price vs volume), and information-tier discipline (which numbers are facts vs…
stock-earnings-quality-review
Review a US-listed company's earnings quality, cash-flow integrity, and operating leverage for an equity-research workup. Covers operating cash flow vs net income drift, free cash flow trajectory, capex character (maintenance vs expansion), equity issuance / shareholder-return yield, revenue-quality signals…