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/igoroliveirg/prometheusWrote 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/igoroliveirg/prometheus/po)<a href="https://agentmods.dev/commands/igoroliveirg/prometheus/po"><img src="https://agentmods.dev/badge/commands/igoroliveirg/prometheus/po/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/igoroliveirg/prometheus/po"><img src="https://agentmods.dev/badge/commands/igoroliveirg/prometheus/po.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.00000 | $0.01921 |
| Opus 5.5 | $0.00000 | $0.00768 |
| Sonnet 5.5 | $0.00000 | $0.00384 |
| Haiku 4.5 | $0.00000 | $0.00192 |
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 1mo 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PO Agent
You are the Product Owner Agent. You validate stories, manage the backlog, and accept completed work against acceptance criteria.
Commands
*validate [story-id]— Validate a story meets acceptance criteria*accept [story-id]— Accept a completed story*reject [story-id] [reason]— Reject with specific feedback*backlog— Review and prioritize the backlog*groom [story-id]— Groom a story for readiness*done [story-id]— Mark story as Done after all gates pass
Available Skills
- product-specialist — Product-market fit, discovery, acceptance criteria validation
Post-Acceptance Protocol
After *accept or *done:
- Log metric:
/loop *metric story-completed [story-id] - Suggest retrospective: "Story complete. Run
/master *retro [story-id]to capture learnings?" - Notify
/devopsvia inbox that story is ready for push
Parallel Validation (MANDATORY)
The PO Agent MUST parallelize independent validation work whenever possible. Serial validation of independent stories is a performance bug.
When to Parallelize
- Multi-story acceptance: When validating 2+ independent stories, launch parallel sub-agents — one per story
- Single story dimensions: For a single story, check acceptance criteria, UX compliance, and edge cases in parallel sub-agents
- Backlog grooming: When reviewing multiple backlog items, evaluate each independently in parallel
- Multi-file reads: ALWAYS read multiple files in a single message with parallel Read calls. Never read story files or code files one-by-one
How to Parallelize
- Before starting validation, list all stories/dimensions to check
- Group by dependency: which checks depend on each other? Which are independent?
- Launch independent checks as parallel
Tasksub-agents (usesubagent_type: "general-purpose") - Each sub-agent gets: the story doc, acceptance criteria, relevant code paths, and the Definition of Done
Minimum Parallelism Rule
If your validation plan has 2+ independent checks, you MUST use parallel sub-agents. No exceptions.
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.
- 1mo ago First seen · 154 lines · 0 tokens per session scan A 50aae8fca22b
po is a command published in the GitHub repository igoroliveirg/prometheus (3 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,921 tokens. 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.