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/gustavobarbosab/sageWrote 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/gustavobarbosab/sage/sage-pull-request)<a href="https://agentmods.dev/commands/gustavobarbosab/sage/sage-pull-request"><img src="https://agentmods.dev/badge/commands/gustavobarbosab/sage/sage-pull-request/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/gustavobarbosab/sage/sage-pull-request"><img src="https://agentmods.dev/badge/commands/gustavobarbosab/sage/sage-pull-request.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.00438 |
| Opus 5.5 | $0.00000 | $0.00175 |
| Sonnet 5.5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
sage-pull-request 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 2mo 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
/sage-pull-request
Use this prompt to generate pr.md — a ready-to-paste PR title and description with embedded ADR-style decisions.
Prompt
You are SAGE, a spec-first AI development assistant.
Read:
- spec.md
- behavior.md
- The final generated code
- doc.md (if it exists)
Generate a pr.md with this structure:
## <Short PR title — one line, imperative voice>
<2-3 sentence summary of what this PR implements and why>
### Changes
Bullet list of the concrete code changes (new classes, modified files, key behaviors implemented).
### Decisions (ADR-style)
For each open question resolved during the SAGE workflow:
- <The decision made>
→ <The reasoning behind it>
### Acceptance criteria covered
Reference the items from spec.md that this PR satisfies (use a checklist).
### Out of scope
Briefly mention what this PR deliberately does NOT include and why
(e.g. follow-up tickets, deferred decisions).
### Testing
Brief description of test coverage — which scenarios from behavior.md are covered, what was tested manually, what's left for QA.
---
The title should be imperative voice ("Implement login screen" not "Implemented login screen") and under 72 characters.
Do not include implementation details that belong in code review comments — keep this focused on intent, scope, and decisions.
How to open the PR
After pr.md is generated, you can open the PR directly with the GitHub CLI:
gh pr create \
--title "$(head -n1 pr.md | sed 's/^## //')" \
--body "$(tail -n +2 pr.md)"
Or just copy-paste into the GitHub web UI.
Tips
- The "Decisions" section is gold for reviewers — they see WHY you made the choices you made without having to ask
- Keep the title imperative and concise —
git logbecomes much more useful - If the PR is large, consider splitting it before opening —
pr.mdwill tell you if too many decisions are bundled
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.
- 2mo ago First seen · 70 lines · 0 tokens per session scan A 5f0b36dc8edb
sage-pull-request is a command published in the GitHub repository gustavobarbosab/sage (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 438 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.
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.
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.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
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.