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.
git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspaceWrote 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/commands/gonzalezpazmonica/pm-workspace/cost-center)<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/cost-center"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/cost-center/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/commands/gonzalezpazmonica/pm-workspace/cost-center"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/cost-center.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.00017 | $0.00733 |
| Opus 5 | $0.00009 | $0.00367 |
| Sonnet 5 | $0.00003 | $0.00147 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
cost-center 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 7d 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.
This is a copy
100% identical to cost-center — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cost Center — Cost Management & Billing
Uso: /cost-center {subcommand} [opciones]
Gestiona todos los aspectos financieros de los proyectos: timesheets, presupuestos, facturación y pronóstico de costes.
Era 38: v2.12.1
Subcommands
1. Log — Registrar horas
/cost-center log --user @monica --date 2026-03-03 --task TASK-2026-0042 --project sala-reservas --hours 7.5 --billable
- Validar: user, project, hours ≥ 0.5
- Leer rates de
.flow-data/rates.json - Calcular cost = hours × rate_for_role
- Crear entrada JSONL:
.flow-data/timesheets/{user}/{YYYY-MM}.jsonl - Actualizar ledger:
.flow-data/ledger/{project}.jsonl - Output: ✅ + horas acumuladas mes
2. Report — Informe de costes
/cost-center report --period 2026-03 --team backend --project sala-reservas
- Filtrar timesheet entries
- Agregar por proyecto/equipo/rol
- Calcular KPIs: cost-per-SP, utilization-rate
- Generar tabla resumen
- Guardar:
output/cost-report-{periodo}.md
3. Budget — Gestión de presupuestos
/cost-center budget --create sala-reservas --total 50000 --currency EUR --start 2026-03-01 --end 2026-06-30
/cost-center budget --burn sala-reservas
Subcomandos internos:
--create {project}: crear presupuesto--update {project}: modificar--burn {project}: mostrar consumo vs. presupuesto--status: tabla all projects
4. Forecast — Pronóstico de costes
/cost-center forecast --project sala-reservas
- Calcular burn_rate = actual_burn / elapsed_time
- Proyectar EAC = burn_rate × total_duration
- Comparar EAC vs. BAC
- Si EAC > BAC: mostrar riesgo + opciones
- Output: gráfico ASCII + recomendaciones
5. Invoice — Generar facturas
/cost-center invoice --client acme-corp --period 2026-03 --status draft
- Recopilar timesheets para cliente+período
- Agrupar por (project, role)
- Generar JSON schema
- Guardar:
output/invoices/{client}-{YYYY-MM}.json - Output: resumen + ruta
Prerequisitos
- @docs/rules/domain/billing-model.md
- @docs/rules/domain/cost-tracking.md
- @.opencode/skills/cost-management/SKILL.md
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.
- 7d ago First seen · 96 lines · 17 tokens per session scan A a2d0a0d13d42
cost-center is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 733 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cost-center, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
cost-center
Cost management and billing — timesheets, budgets, forecasting, invoicing.
earned-value-mgmt
Track the financial progress of a large project.
deal-health
Summarize deal health, open actions, and meeting-prep blockers from OloLand's deal-health surface.
arckit.sobc
Create Strategic Outline Business Case (SOBC) using UK Government Green Book 5-case model.
review-goals
Review all active financial goals, update their progress, flag at-risk goals, and recommend adjustments. Reads from and writes to financial-goals/active/.
gsd:add-backlog
Add an idea to the backlog parking lot (999.x numbering).