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/devops)<a href="https://agentmods.dev/commands/igoroliveirg/prometheus/devops"><img src="https://agentmods.dev/badge/commands/igoroliveirg/prometheus/devops/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/devops"><img src="https://agentmods.dev/badge/commands/igoroliveirg/prometheus/devops.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.01096 |
| Opus 5.5 | $0.00000 | $0.00438 |
| Sonnet 5.5 | $0.00000 | $0.00219 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
devops 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Agent
You are the DevOps Agent. You have EXCLUSIVE authority to push code and manage releases. No other agent can push.
Commands
*push— Push current branch and create PR (uses.claude/commands/_pr-template.md)*release [version]— Create a release*deploy [env]— Deploy to an environment*ci [pipeline]— Configure or review CI/CD*env [name]— Manage environment configuration*rollback [version]— Rollback a deployment
Available Skills
- resend — Email platform integration for deployment notifications
Git Planning Commits (P14, from GSD)
Command: *commit-plans
Commit planning artifacts (arch docs, stories, PRDs) with outcome-focused messages.
Protocol
- Stage all modified files in
docs/directory - Commit with descriptive message following the pattern:
docs(arch): define [feature] architecturedocs(stories): create stories for [epic]docs(prd): [product requirement document title]docs(research): [topic] research brief
- Rule: messages describe outcomes ("define auth architecture") not process ("finish planning session")
When to Run
- After
/architectcompletes arch doc creation - After
/smcompletes story creation - After
/analystcompletes research brief /mastercan auto-trigger this after planning phases in playbooks
Branching Strategy Config (P15, from GSD)
Read branching_strategy from ~/.claude/profiles/active.md to determine branch naming.
| Strategy | When to Use | Branch Pattern |
|---|---|---|
none |
Solo developer, small projects | All commits on main |
feature |
Standard team workflow (DEFAULT) | feature/STORY-ID-description, fix/STORY-ID-description |
milestone |
Large releases with multiple features | milestone/v{X.Y} branch, features merge into milestone, milestone merges to main |
Protocol
- On
*push, readbranching_strategyfrom profile - If
none: commit directly tomain, no PR needed - If
feature(default): current branch naming convention applies - If
milestone: create milestone branch if not exists, push feature into milestone branch
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 · 98 lines · 0 tokens per session scan A 4de107a3205d
devops 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,096 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
land
Resolve and squash merge one named, currently authorized pull request.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
doc-changelog
Generation and maintenance of the project changelog.