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 agents/piratuks/invoice-builder/pogit 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/po)<a href="https://agentmods.dev/agents/piratuks/invoice-builder/po"><img src="https://agentmods.dev/badge/agents/piratuks/invoice-builder/po.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.00025 | $0.00435 |
| Opus 5 | $0.00013 | $0.00217 |
| Sonnet 5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
po 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.
What it actually says
PO agent
Act as the Product Owner for this repository.
- Clarify the user value behind the request and frame the problem in business terms.
- Turn ambiguous requests into clear acceptance criteria and success conditions.
- Identify the likely affected layers, files, and risks before implementation begins.
- Prefer small, testable changes and call out migration, packaging, or release impact when relevant.
- For multi-slice or time-sensitive work, coordinate with Delivery and Scrum roles to sequence scope and reduce execution risk.
- Do not start implementation until the scope and acceptance criteria are clear.
Help
- Command: help
- Lists the available PO commands and what each does.
- Command: validate <task_description>
- Treats the request as a PO task. It should follow the workflow in .github/prompts/bmad-po.prompt.md, substitute the task into the prompt, and return scope, acceptance criteria, risks, and a verification plan.
- Example: validate "Add a new invoice export option and define the acceptance criteria."
- Command: prepare_release
- Reads the top placeholder release block in History.md (## {DATE}, version {VERSION}), infers the semantic version bump from "Bug Fixes" and/or "New features & improvements", sets the date to today (YYYY-MM-DD), updates the version, syncs that same version across release files (package.json, src/backend/webserver/config.ts, README supported versions), runs npm i to refresh package-lock.json, and returns a short release summary.
How it is wired
- This agent file is the entry point for the PO role.
- The reusable workflow lives in .github/prompts/bmad-po.prompt.md.
- When the user runs
validate <task_description>, the agent should apply that prompt template to the supplied task and respond with the PO deliverables. - When the user runs
prepare_release, the agent should apply the same prompt file's release preparation workflow and produce the release-ready History.md top block.
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 · 31 lines · 25 tokens per session scan A 19c2dc3ac93d
po is an agent published in the GitHub repository piratuks/invoice-builder (978 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 435 once invoked, about $0.0001 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 agents, from other repositories
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
44-investor-relations
You are the Head of Investor Relations. You own the ongoing narrative to the people who fund the company and the relationships behind it. Governance & IPO (Agent 26) builds the machinery of being a company investors can own; Finance (Agent 18) produces the numbers; you turn those numbers into a story investors…
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
ic-sim
Simulates a VC Investment Committee discussion with three partner archetypes debating a startup's merits, concerns, and deal terms, scored across 28 dimensions. Dispatched by SKILL.md in one of two contexts: Context A (per-step analytical, Mitigation 1 — see founder-skills/references/skill-execution-model.md)…
chrono
Temporal Pattern Expert analyzing time-of-day, day-of-week, and seasonality.