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/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/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/instructions/piratuks/invoice-builder/agents-md"><img src="https://agentmods.dev/badge/instructions/piratuks/invoice-builder/agents-md.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.01792 | $0.01792 |
| Opus 5.5 | $0.00717 | $0.00717 |
| Sonnet 5.5 | $0.00358 | $0.00358 |
| Haiku 4.5 | $0.00179 | $0.00179 |
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 26d 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 — 152 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: apps/renderer/src
- Electron main process: apps/desktop/main
- Preload bridge: apps/desktop/preload/preload.ts
- Webserver: apps/server
- Documentation website (Docusaurus, builds docs/ content): apps/website
- Shared backend services, database infrastructure, and migrations: packages/core
- Shared public DTOs, enums, and IPC contracts: packages/contracts
- Documentation pages: docs/guides (screenshots: docs/guides/images, layout JSON examples: docs/guides/examples)
- End-to-end tests: e2e/desktop and e2e/web
- Root orchestration: Docker, packaging, releases, and cross-workspace scripts
Workspace and runtime conventions
- Run npm installs, updates, and dependency pruning from the repository root. Keep the single
package-lock.jsonat the root; do not create workspace-local lockfiles. - Declare dependencies in the workspace that owns them. The root manifest is reserved for shared orchestration, testing, packaging, and release tooling.
- Exception:
sqlite3is also listed as a rootdependenciesentry even thoughpackages/coreowns it.electron-builder(26.3.0+) determines whichnode_modulesto include in a packaged build by walking the rootpackage.json'sdependencies; with an empty rootdependencies, it silently ships zeronode_modules, breaking any native module required at runtime by the Electron main process (seeapps/desktop/vite.main.config.tsrollupOptions.external). Do not remove this entry without re-verifying packaging vianpx electron-builder --config apps/desktop/electron-builder.yml --win --x64 --dirandnpx asar list release/win-unpacked/resources/app.asar | findstr sqlite3.
- Exception:
- Run a workspace command with
npm run <script> -w @invoice-builder/<workspace>; use root scripts only for cross-workspace workflows. - npm may hoist packages to the root
node_modules. Do not manually manage workspacenode_modulesdirectories. - Treat
dist-renderer/,dist-desktop/,dist-server/, anddist-migrations/as generated build output. Local runtime data belongs inapp-data/; containers use/app-data. - Use Node 24 LTS or a supported later release. Node 25 is outside the engine ranges declared by the current Vitest and jsdom versions.
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.
- 26d ago Changed · +1 lines · +163 tokens per session 94d4459f064f
- 27d ago Changed · +18 lines · +391 tokens per session 2ef1c155d3b3
- 2mo 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 (1,344 stars, last pushed 3d ago), licensed MIT. It adds 1,792 tokens to every session, about $0.0072 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.