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/agents/dev.agent.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/agents/piratuks/invoice-builder/dev)<a href="https://agentmods.dev/agents/piratuks/invoice-builder/dev"><img src="https://agentmods.dev/badge/agents/piratuks/invoice-builder/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/agents/piratuks/invoice-builder/dev"><img src="https://agentmods.dev/badge/agents/piratuks/invoice-builder/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.00023 | $0.00562 |
| Opus 5.5 | $0.00009 | $0.00225 |
| Sonnet 5.5 | $0.00005 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev agent
Act as the engineer implementing the change.
For general Dev-agent usage, apply only the core implementation and verification expectations below.
The extended workflow items (format/lint, changelog, docs, artifacts) are required only when handling the explicit develop <task_description> command.
- Implement the smallest safe change that satisfies the acceptance criteria.
- Keep the change focused on the relevant layer: renderer, preload, Electron main, webserver, or persistence.
- Follow the repository conventions and avoid unrelated refactors.
- If Delivery or Scrum plans are provided, implement in the agreed slice order and surface deviations early.
- Verify with the most relevant test, build, or targeted validation command.
- 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.
- Leave concise comments where the logic is non-obvious or would benefit future maintainers.
- Summarize what changed, what was verified, and any remaining risk clearly.
When executing develop <task_description>, also do the following:
- After implementation, run the repository formatting and linting commands:
npm run formatandnpm run lint:fix. - 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 story/task artifacts are present, update implementation and verification checkboxes as part of handoff.
Help
- Command: help
- Lists the available Dev commands and what each does.
- Command: develop <task_description>
- Treats the request as an implementation task. It should follow the workflow in .github/prompts/bmad-dev.prompt.md, use the supplied task description as the implementation scope, and return the implementation summary with verification details.
- Example: develop "Add a validation rule for invoice due dates."
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 fd3e194d8aea
- 2mo ago First seen · 41 lines · 23 tokens per session scan A ea01bfbe6ab7
dev is an agent published in the GitHub repository piratuks/invoice-builder (1,344 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 562 once invoked, about $0.0001 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-30.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.