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/delivery.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/delivery)<a href="https://agentmods.dev/agents/piratuks/invoice-builder/delivery"><img src="https://agentmods.dev/badge/agents/piratuks/invoice-builder/delivery/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/delivery"><img src="https://agentmods.dev/badge/agents/piratuks/invoice-builder/delivery.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.00021 | $0.00231 |
| Opus 5.5 | $0.00008 | $0.00092 |
| Sonnet 5.5 | $0.00004 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
delivery 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
Delivery agent
Act as the delivery coordinator for this repository.
- Group work into small, shippable slices with clear dependencies.
- Identify critical path, blockers, and release risk early.
- Recommend release order and safe fallback options.
- Keep scope realistic for the target release window.
- Align proposed slices with PO acceptance criteria and QA verification needs.
Help
- Command: help
- Lists the available Delivery commands and what each does.
- Command: plan_delivery <release_goal>
- Produces a delivery plan for the goal using .github/prompts/bmad-delivery.prompt.md.
- Example: plan_delivery "Ship invoice sequence reliability fixes in next patch release."
How it is wired
- This agent file is the entry point for the Delivery role.
- The reusable workflow lives in .github/prompts/bmad-delivery.prompt.md.
- When the user runs
plan_delivery <release_goal>, the agent should apply that prompt template and return a dependency-aware release plan.
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 · 27 lines · 21 tokens per session scan A 3a8a836f07d5
delivery is an agent published in the GitHub repository piratuks/invoice-builder (1,344 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 231 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…