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.
npx agentmods add commands/igoroliveirg/prometheus/_pr-templategit clone --depth 1 https://github.com/igoroliveirg/prometheusWhat 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 | $0.00000 | $0.00500 |
| Opus 5 | $0.00000 | $0.00250 |
| Sonnet 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 2d 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.
- 2d 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 6mo 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.