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 board-prepgit 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/board-prep)<a href="https://agentmods.dev/skills/davekilleen/dex/board-prep"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/board-prep/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/board-prep"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/board-prep.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.00044 | $0.01103 |
| Opus 5.5 | $0.00018 | $0.00441 |
| Sonnet 5.5 | $0.00009 | $0.00221 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
board-prep 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Use for a named board or leadership meeting when the requester needs a traceable financial snapshot, variance narrative, forecast limits, and questions for human review. Confirm the reporting period and meeting scope before gathering data.
Do not use this skill to close the books, post or alter accounting entries, certify an audit, approve a forecast, make a board decision, or send materials externally. Not for tax, legal, fundraising, or investor filings that require an authorized professional process.
Inputs and source discipline
- Record the requested period, meeting date if supplied, reporting timezone/fiscal calendar,
and an explicit
as-ofdate. Never invent a missing date; mark it unknown and ask for it. For every input record the source, source date, date checked, scope, unit, and currency. - Prefer reconciled ledger or close-package actuals, then an approved budget or forecast, then dated management reports, then dated meeting notes or user statements. Treat meeting context as context, not as proof of a financial number. Keep conflicting sources visible.
- Keep actuals, budget, forecast, and scenario values in separate fields. Normalize units or currency only with an explicit conversion source, rate, and date; otherwise report them as incomparable. Do not turn a missing value into zero.
Method
- Start read-only with a source inventory. Capture the source references and a metric ledger for revenue, expenses, cash, and other requested measures: value, period, as-of date, unit, currency, formula or basis, source, and confidence.
- Reconcile reported actuals to their supplied subtotals and totals before narrating them. Show actual-versus-budget and actual-versus-forecast comparisons only when periods, units, and currencies are comparable. Apply a stated materiality convention; if none is supplied, say materiality was not assessed rather than choosing a threshold.
- Describe only evidenced changes. Label a forecast with its source, horizon, assumptions, and limits; do not extend it beyond the supplied horizon or imply certainty. Separate observed facts, inferred context, open questions, and proposed discussion points.
- Prepare likely board questions as questions with supporting evidence or an explicit unknown. End with a draft for human review, not a claim that the board packet is approved.
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 74815808c317
- 1mo ago First seen · 87 lines · 44 tokens per session scan A 1b11c57af1d7
board-prep is a skill published in the GitHub repository davekilleen/Dex (508 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 1,103 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…