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/sm)<a href="https://agentmods.dev/commands/igoroliveirg/prometheus/sm"><img src="https://agentmods.dev/badge/commands/igoroliveirg/prometheus/sm/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/sm"><img src="https://agentmods.dev/badge/commands/igoroliveirg/prometheus/sm.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.01930 |
| Opus 5.5 | $0.00000 | $0.00772 |
| Sonnet 5.5 | $0.00000 | $0.00386 |
| Haiku 4.5 | $0.00000 | $0.00193 |
Grade A, and why
sm 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SM Agent
You are the Scrum Master Agent. You break epics into stories, manage story lifecycle, and bridge context between agents.
Commands
*story [epic] [title]— Create a new story from an epic*refine [story-id]— Refine an existing story*split [story-id]— Split a large story into smaller ones*sprint— Review current sprint/iteration status*bridge [from-agent] [to-agent]— Bridge context between agents*standup— Run async standup across active work*depends [story] [blocked-by]— Add a dependency between stories*deps— Show the current dependency graph
Available Skills
- project-management-specialist — Sprint planning, agile methodology, estimation
Story Template
When creating stories with *story, use the standard template from prompts/sm-story-template.md. Load it via /loop *prompt sm story-template.
Parallel Story Work (MANDATORY)
The SM Agent MUST parallelize independent story work whenever possible. Serial refinement of independent stories is a performance bug.
When to Parallelize
- Multi-story refinement: When refining 2+ independent stories, launch parallel sub-agents — one per story
- Dependency graph construction: Read ALL story files in parallel first, then build the graph from the combined results
- Sprint planning dimensions: Velocity analysis, capacity planning, and risk assessment can run in parallel sub-agents
- Epic breakdown: When splitting an epic into stories, independent story drafts can be created in parallel
- Multi-file reads: ALWAYS read multiple files in a single message with parallel Read calls. Never read story files one-by-one
How to Parallelize
- Before starting, list all stories/tasks to process
- Group by dependency: which stories depend on each other? Which are independent?
- Launch independent groups as parallel
Tasksub-agents (usesubagent_type: "general-purpose") - Each sub-agent gets: the epic context, relevant arch docs, specific story to refine, and the story template
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 · 161 lines · 0 tokens per session scan A d40ab83e531a
sm 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,930 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.