Invoice Builder is an offline desktop application for creating, managing, and exporting invoices and quotations, with business data stored in a local database file. It is designed for freelancers, contractors, and small businesses that need local control of their invoicing data and PDF documents. The catalogue commands, agents, and instructions provide coding-agent workflows for working with the application.
Borrowing it
Nothing to install: this file belongs to piratuks/invoice-builder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/piratuks/invoice-builder/main/.github/prompts/bmad-dev.prompt.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/commands/piratuks/invoice-builder/bmad-dev)<a href="https://agentmods.dev/commands/piratuks/invoice-builder/bmad-dev"><img src="https://agentmods.dev/badge/commands/piratuks/invoice-builder/bmad-dev/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/commands/piratuks/invoice-builder/bmad-dev"><img src="https://agentmods.dev/badge/commands/piratuks/invoice-builder/bmad-dev.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.00000 | $0.00474 |
| Opus 5.5 | $0.00000 | $0.00190 |
| Sonnet 5.5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
bmad-dev 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 27d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMAD dev prompt
Use this prompt for implementation once the scope and acceptance criteria are clear.
Invocation
- Command: help
- Lists the available Dev commands and what each does.
- Command: develop <task_description>
- This is the workflow behind the Dev agent's
developcommand. When invoked, substitute the task description into{{TASK_DESCRIPTION}}and implement the change according to the scope and acceptance criteria supplied by the PO output. - Example: develop "Add a validation rule for invoice due dates."
Task
{{TASK_DESCRIPTION}}
Role
Act as the developer implementing the change.
Instructions
- Implement the smallest safe change that satisfies the scope.
- Keep the change focused on the relevant layer.
- If Delivery or Scrum plans are provided, implement in agreed slice order and surface deviations early.
- Verify with the most relevant command(s).
- Check for TypeScript issues in the affected files and fix them before finishing. Treat errors such as possibly undefined values, unsafe property access, or other type mismatches as required fixes, not optional cleanup.
- After implementation, run
npm run formatandnpm run lint:fixto ensure formatting and linting are corrected. - Update docs/history.md with a new entry at the top. Add the {DATE}, {VERSION} as placeholders and describe the change under either "New features & improvements" or "Bug Fixes".
- Update README.md and the relevant page(s) under docs/guides/ when the change impacts setup, usage, behavior, or screenshots.
- If documentation needs a new or updated image, add a
{IMAGE}placeholder where the image should be inserted. - If shared story/task artifacts are used under
artifacts/, update implementation checklist and verification notes before handoff; do not create new artifact instances by default. - Leave concise comments where the logic is non-obvious or would benefit future maintainers.
- Summarize what changed, what was verified, and any residual risk.
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.
- 27d ago Changed d4491a0380a9
- 1mo ago First seen · 36 lines · 0 tokens per session scan A fc913e77e4c3
bmad-dev is a command published in the GitHub repository piratuks/invoice-builder (1,344 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 474 tokens. 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-08.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.