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 jikig-ai/soleur --skill invoicegit clone --depth 1 https://github.com/jikig-ai/soleurWrote 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/jikig-ai/soleur/invoice)<a href="https://agentmods.dev/skills/jikig-ai/soleur/invoice"><img src="https://agentmods.dev/badge/skills/jikig-ai/soleur/invoice/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/jikig-ai/soleur/invoice"><img src="https://agentmods.dev/badge/skills/jikig-ai/soleur/invoice.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.00050 | $0.03753 |
| Opus 5 | $0.00025 | $0.01877 |
| Sonnet 5 | $0.00010 | $0.00751 |
| Haiku 4.5 | $0.00005 | $0.00375 |
Grade A, and why
invoice 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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 196 lines · 50 tokens per session scan A e70904055002
invoice is a skill published in the GitHub repository jikig-ai/soleur (15 stars, last pushed today), with no licence file. It adds 50 tokens to every session and 3,753 once invoked, about $0.0003 per session on Opus 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-04.
Other skills, from other repositories
model-cost-compare
Starter: compare model costs for a described task — maps task shape to the cheapest adequate seat and shows the price spread.
flow-define
Multi-AI requirements scoping using available external providers (Double Diamond Define phase). Priority triggers: octo define, octo scope, co-define, co-scope. DO NOT use for implementation, research, review/validation, or built-in commands.
flow-discover
Multi-AI research using available external providers (Double Diamond Discover phase).
flow-spec
NLSpec authoring — use when you need a structured specification from multi-AI research and consensus.
skill-design-lineage
Persist design documents with branch tracking, revision chains, and cross-session discovery.
octopus-architecture
Review system architecture, simplify boundaries, or compare interface designs from repository evidence.