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 Ootto-AI/claude-invoice-skills --skill invoice-chasergit clone --depth 1 https://github.com/Ootto-AI/claude-invoice-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/ootto-ai/claude-invoice-skills/invoice-chaser)<a href="https://agentmods.dev/skills/ootto-ai/claude-invoice-skills/invoice-chaser"><img src="https://agentmods.dev/badge/skills/ootto-ai/claude-invoice-skills/invoice-chaser/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/ootto-ai/claude-invoice-skills/invoice-chaser"><img src="https://agentmods.dev/badge/skills/ootto-ai/claude-invoice-skills/invoice-chaser.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.00061 | $0.00547 |
| Opus 5.5 | $0.00024 | $0.00219 |
| Sonnet 5.5 | $0.00012 | $0.00109 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
invoice-chaser 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 2mo 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.
What it actually says
Invoice Chaser
Draft a payment reminder whose firmness matches how overdue the invoice is.
When to use
A client hasn't paid and you need a reminder that fits how late it is — friendly for a few days, firmer for a few weeks.
What you'll need
Client/contact name, invoice number + amount, original due date, days overdue, prior reminders sent, and the relationship.
Instructions
Collect any missing inputs from the user, then run this prompt:
You are my accounts-receivable assistant. Write a payment reminder email for an overdue invoice.
Details:
- Client / contact name: [client name]
- Invoice number and amount: [invoice # and amount]
- Original due date: [due date]
- Days overdue: [number of days]
- Prior reminders sent: [none / one / two — and roughly when]
- Relationship: [new client / long-standing / large account]
Match the tone to how overdue it is:
- 1-14 days: warm, assume it slipped through. Friendly nudge.
- 15-30 days: polite but clearer. Ask for a specific pay-by date.
- 31-60 days: firm and direct. State the amount, the due date, and request payment this week.
- 60+ days: serious. Note next steps (pause on work / late fee / collections) without threatening.
Write a subject line and a short email (under 150 words). Plain language, no guilt-tripping, no jargon. Make it easy to pay: restate the amount, invoice number, and a clear single ask. End with one specific question that prompts a reply. Give me 2 subject line options.
Tip: Give the exact days overdue, not "a while ago" — matching firmness to lateness is the whole point.
Built by Ootto — the AI autopilot that connects your tools once and runs invoicing, follow-up, and reports for you, automatically. Book a demo →
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.
- 2mo ago First seen · 55 lines · 61 tokens per session scan A b28f0a8757ca
invoice-chaser is a skill published in the GitHub repository Ootto-AI/claude-invoice-skills (1 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 547 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-31.
invoice-chaser compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| invoice-chaserOotto-AI/claude-invoice-skills | Skill | 1 | 4mo ago | MIT | A | 61 | Claude Code |
| pandadoc-invoice-handoffPandaDoc/mcp-server-guide | Skill | 3 | yesterday | MIT | A | 65 | Claude Code |
| visma-eaccountingjiraporn-junext/visma-eaccounting-skill | Skill | 1 | 9mo ago | MIT | B | 90 | Claude Code, Codex |
| ma-playbookalirezarezvani/claude-skills | Skill | 29k | 3d ago | MIT | A | 29 | Claude Code |
| fiscalisteromainsimon/paperasse | Skill | 2.6k | 2d ago | MIT | A | 320 | Claude Code, Codex |
| comptableromainsimon/paperasse | Skill | 2.6k | 2d ago | MIT | A | 153 | Claude Code, Codex |
| syndicromainsimon/paperasse | Skill | 2.6k | 2d ago | MIT | A | 204 | Claude Code, Codex |