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 SkillMedev/skills --skill expense-policygit clone --depth 1 https://github.com/SkillMedev/skillsWrote 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/skillmedev/skills/expense-policy)<a href="https://agentmods.dev/skills/skillmedev/skills/expense-policy"><img src="https://agentmods.dev/badge/skills/skillmedev/skills/expense-policy/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/skillmedev/skills/expense-policy"><img src="https://agentmods.dev/badge/skills/skillmedev/skills/expense-policy.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.00126 | $0.01566 |
| Opus 5.5 | $0.00050 | $0.00626 |
| Sonnet 5.5 | $0.00025 | $0.00313 |
| Haiku 4.5 | $0.00013 | $0.00157 |
Grade A, and why
expense-policy 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 11d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expense and Approval Policy
An expense policy that employees ignore is worse than no policy - it creates a false sense of control while spend leaks through exceptions. A good policy is short enough to read, specific enough to apply, and enforced consistently; the costly mistake this skill prevents is the prose-heavy policy nobody can apply at the moment of purchase, which converts every expense into a judgment call and every judgment call into precedent.
Operating procedure
Order matters: limits must be calibrated to the company before the approval matrix is drawn, or the tiers will not match how spend actually flows.
- Collect the inputs below.
- Draft the five mandatory sections in order: what is reimbursable, spend limits by category, approval authority by amount, documentation requirements, submission deadlines. Each section is a table or short bulleted list - never prose paragraphs. An employee must be able to scan to any answer in under 30 seconds.
- Calibrate the default numbers below to the company's size, geography, and travel intensity. Keep the structure even where the numbers move.
- Add the enforcement section - a policy without stated consequences is a suggestion.
- Close the catch-all: anything not listed is not reimbursable without explicit pre-approval.
- Route the draft to finance and legal for sign-off before publication, and pair with the expense-tool configuration so approval tiers are enforced in software, not memory.
Step 1: gather inputs
- Company headcount and typical approver chain (who exists between employee and CFO).
- Travel intensity: domestic vs international mix, typical destinations (sets the hotel cap - default to the median business-hotel rate in each frequent city).
- Existing pain points: which categories currently leak (default guess: meals, software subscriptions, and late submissions - label this a guess until finance confirms).
- Finance system in use and its approval-routing capability.
- Currency (defaults below are USD).
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.
- 11d ago Changed · +2 lines · -2 tokens per session d912e2d35fbe
- 1mo ago First seen · 101 lines · 128 tokens per session scan A 1b4857ede392
expense-policy is a skill published in the GitHub repository SkillMedev/skills (19 stars, last pushed 3d ago), licensed MIT. It adds 126 tokens to every session and 1,566 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
collections-email
Write a polite-but-firm payment-reminder / collections email sequence for overdue invoices. Use when asked to write a collections email, a payment reminder, a dunning sequence, or to chase an overdue invoice. Produces a staged sequence — gentle pre-due nudge through escalating overdue reminders to a final notice …
financial-statement-explainer
Explain a financial statement (P&L, balance sheet, or cash flow) in plain English. Use when asked to explain a P&L / income statement, a balance sheet, a cash flow statement, or to make financials understandable to a non-finance reader. Produces a plain-language walkthrough — what each section means, the line items…
agent-era-pricing
Redesign seat-based pricing for the agent era — when one human runs ten agents, per-seat models collapse. Use when agents are eroding seat counts, when asked to migrate to usage- or outcome-based pricing, to price an agent/API tier, or to defend revenue as customers automate their own usage. Produces a pricing…
ib-collar
Generate tactical collar strategy reports for protecting PMCC positions through earnings or high-risk events. Requires TWS or IB Gateway running locally.
report-stock
Generate comprehensive stock analysis report (PDF or markdown) with trend, PMCC, and fundamental analysis.
ib-report-delta-adjusted-notional-exposure
Report delta-adjusted notional exposure across all IBKR accounts. Calculates option deltas using Black-Scholes and reports long/short exposure by account and underlying. Use when user asks about delta exposure, portfolio risk, or directional exposure.