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/_pr-template)<a href="https://agentmods.dev/commands/igoroliveirg/prometheus/_pr-template"><img src="https://agentmods.dev/badge/commands/igoroliveirg/prometheus/_pr-template/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/_pr-template"><img src="https://agentmods.dev/badge/commands/igoroliveirg/prometheus/_pr-template.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.00500 |
| Opus 5.5 | $0.00000 | $0.00200 |
| Sonnet 5.5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
_pr-template 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.
What it actually says
PR Template
Used by /devops *push to generate PR descriptions. Pulls data from story docs, dev records, QA results, and arch docs.
Template
When creating a PR, /devops should generate this structure:
PR Title Format
type(scope): description [STORY-XXX]
PR Body Template
## Story
**[STORY-XXX: Title](link-to-story-doc)**
## Summary
<!-- Brief description of what this PR does and why -->
## Architecture Reference
<!-- Link to arch doc, key design decisions -->
- Arch doc: `docs/architecture/[feature].md`
## Changes
<!-- Pulled from dev record in story doc -->
| File | Action | Description |
|------|--------|-------------|
## Testing
<!-- Pulled from QA results in story doc -->
- [ ] Unit tests added/updated
- [ ] Integration tests (if applicable)
- [ ] E2E tests (if applicable)
- [ ] Manual testing completed
## QA Review
<!-- Pulled from QA section of story doc -->
- Quality gate: Pass / Fail
- Issues found: X (all resolved)
- Recommendation: Approve / Request Changes
## Acceptance Criteria
<!-- Pulled from story doc -->
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
## Screenshots
<!-- If UI changes, add before/after screenshots -->
## Checklist
- [ ] Code follows project conventions
- [ ] Arch doc compliance verified
- [ ] Tests passing
- [ ] No security vulnerabilities
- [ ] Accessibility requirements met
- [ ] Story dev record updated
- [ ] QA results documented
## Story Link
`docs/stories/STORY-XXX-description.md`
How DevOps Uses This
When /devops *push is called:
- Read the active story from
.claude/state/current.md - Read the story doc from
docs/stories/ - Read the arch doc referenced in the story
- Pull the dev record section (files changed, implementation notes)
- Pull the QA results section (quality gate, issues, recommendation)
- Pull acceptance criteria
- Fill in the PR template
- Create PR with
gh pr create - Report PR URL
- Log to audit: "PR created for STORY-XXX"
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 · 81 lines · 0 tokens per session scan A f30c59c24dfc
_pr-template 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 500 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
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
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.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
codex-review
Use when asked to check, turn on, turn off, or switch this repo's Codex review mode (local, github, or off), or to report the effective mode and Codex sandbox status.