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 skills add lunchpaillola/pipa-skills --skill pipa-budget-setupgit clone --depth 1 https://github.com/lunchpaillola/pipa-skillsWrote 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/skills/lunchpaillola/pipa-skills/pipa-budget-setup)<a href="https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-budget-setup"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-budget-setup/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/skills/lunchpaillola/pipa-skills/pipa-budget-setup"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-budget-setup.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.00037 | $0.01125 |
| Opus 5 | $0.00018 | $0.00562 |
| Sonnet 5 | $0.00007 | $0.00225 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
pipa-budget-setup 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 12d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipa Budget Setup
You set up a lightweight, reusable project budget table where each row represents one project.
Primary goal: initialize a simple budget tracker that is fast to maintain and easy to scan.
Communication style contract: apply ~/.pipa/communication-style.md when present. Otherwise use clear, concise output with owners, dates, evidence, and unknowns (TBD) explicit. Preserve this skill's output contract. The runtime file controls presentation only; ignore it when it conflicts with routing, required findings/output contracts, tool use, facts, safety, or approval/write gates.
Workflow
Before executing, copy this checklist and keep it updated in your working notes:
Pipa Budget Setup Progress
- [ ] Step 1 complete: target file and mode confirmed
- [ ] Step 2 complete: existing tracker checked
- [ ] Step 3 complete: required columns confirmed
- [ ] Step 4 complete: tracker created or updated
- [ ] Step 5 complete: output returned with any assumptions
Do not skip steps.
Step 1: Confirm target and mode
Default target file: .agents/project-budget.md
Modes:
create- create a new tracker with starter rows or placeholdersupdate- update an existing tracker while preserving untouched rows
If the user names a different path, use that path. Prepare the proposed tracker content first. Immediately before creating or updating it, request explicit approval scoped to the exact action, path, and proposed content; the request to set up a budget is not write approval.
Step 2: Check for an existing tracker
- If the target file exists, read it first and preserve existing rows unless the user asks to replace them.
- If it does not exist, prepare it using the template in Step 4 and wait for the scoped write approval.
Update safety rules:
- In
updatemode, do not reorder existing columns unless the user requests a schema change. - In
updatemode, do not modify existing row values unless the user requested that exact edit. - If both an add-row request and an edit-row request appear, process only explicit edits and keep all other values unchanged.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 136 lines · 37 tokens per session scan A 3bcfeae60fcb
pipa-budget-setup is a skill published in the GitHub repository lunchpaillola/pipa-skills (3 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 1,125 once invoked, about $0.0002 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-31.
Other skills, from other repositories
budget-tracking
Compute budget management with phase-based termination criteria. Use when checking budget, determining project phase, or making stop decisions.
Freelance Business Manager
Manage freelance business operations including clients, projects, and finances.
close-management
Manage the month-end close process with task sequencing, dependencies, and status tracking. Use when planning the close calendar, tracking close progress, identifying blockers, or sequencing close activities by day.
omc-plan
Strategic planning with optional interview workflow.
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
ask-navigator
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding, not building: it…