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 agentmods add instructions/piratuks/invoice-builder/agents-mdgit clone --depth 1 https://github.com/piratuks/invoice-builderWrote 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/instructions/piratuks/invoice-builder/agents-md)<a href="https://agentmods.dev/instructions/piratuks/invoice-builder/agents-md"><img src="https://agentmods.dev/badge/instructions/piratuks/invoice-builder/agents-md.svg" alt="Measured on agentmods" 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 | $0.01238 | $0.01238 |
| Opus 5 | $0.00619 | $0.00619 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
invoice-builder AGENTS.md 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 4d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent workflow for Invoice Builder
This repository follows a lightweight BMAD-style workflow for coding tasks.
Operating model
- Plan before coding: identify the requested outcome, affected layers, and verification steps.
- Keep changes focused: prefer a narrow implementation over broad refactors.
- Verify before claiming completion: run the relevant tests or build checks and report the result.
- Keep the handoff clear: summarize what changed, evidence gathered, and any remaining risk.
When to use this workflow
Use this workflow for:
- new features
- bug fixes
- UI changes
- IPC or preload changes
- backend or webserver changes
- persistence or migration work
Repository map
- Renderer/UI: src/renderer
- Electron main process: src/backend/main
- Preload bridge: src/preload/preload.ts
- Webserver: src/backend/webserver
- Database and migrations: src/backend/shared
Default workflow
- Read the request and identify the likely runtime layer.
- List the files that are likely to change.
- Implement the smallest safe solution.
- Run the relevant verification command(s).
- Report the outcome and any follow-up suggestions.
Quick start (issue -> done)
Use this sequence for a typical GitHub issue:
po validate <issue_summary>- clarify user value, acceptance criteria, risks, and verification plan.delivery plan_delivery <release_goal>- optional for multi-slice or timeline-sensitive changes.scrum plan_sprint <sprint_goal>- optional when managing several active issues.dev develop <implementation_task>- implement in agreed slice order and run relevant checks.qa review <implemented_task>- verify acceptance criteria, regressions, evidence, and state progression.- Move state through
draft->validated->in-dev->qa-review->done.
If the issue is small, you can skip Delivery and Scrum and run po -> dev -> qa.
Routing guide:
- Small issue:
po -> dev -> qa - Medium issue:
po -> delivery -> dev -> qa - Large or multi-session issue:
po -> delivery -> scrum -> dev -> qa
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.
- 4d ago First seen · 133 lines · 1,238 tokens per session scan A a0b476e6b921
invoice-builder AGENTS.md is an instructions file published in the GitHub repository piratuks/invoice-builder (978 stars, last pushed today), licensed MIT. It adds 1,238 tokens to every session, about $0.0062 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-08-30.
Other instructions, from other repositories
Convertible-Bond-Pricing-Research CLAUDE.md
Instructions for ericxuzhesheng/Convertible-Bond-Pricing-Research, covering claude.md — convertible bond pricing research, current published state and routine commands.
swiss-snb-mcp CLAUDE.md
Claude Code instructions for malkreide/swiss-snb-mcp, covering claude.md, teil 1 — konventionen (portfolio-weit), vor der arbeit, tests and wenn etwas rot ist.
bullet-bots AGENTS.md
Instructions for bulletxyz/bullet-bots, covering bullet-bots, build & test, run the faucet curl printed by keygen, then, or (base58 from phantom/delegation export, or hex) and architecture — the harness, feeds, and actors.
romaco-mcp AGENTS.md
AGENTS.md instructions for romaco-labs/romaco-mcp, covering purpose, read first, product boundaries, architecture invariants and development method.
financial-services-plugins-new CLAUDE.md
Claude Code instructions for yuping322/financial-services-plugins-new, covering financial services plugins, repository structure, plugin structure, key files and development workflow.
zenmoney-mcp CLAUDE.md
Claude Code instructions for sakost/zenmoney-mcp, covering zenmoney mcp server — development guidelines, project overview, build & test, architecture and coding standards.