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 rules/gustavobarbosab/sage/sage-prgit 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/rules/gustavobarbosab/sage/sage-pr)<a href="https://agentmods.dev/rules/gustavobarbosab/sage/sage-pr"><img src="https://agentmods.dev/badge/rules/gustavobarbosab/sage/sage-pr.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00382 |
| Opus 5 | $0.00006 | $0.00191 |
| Sonnet 5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
sage-pr 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 4d 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 pr
Generates pr.md — a ready-to-paste PR title and description with ADR-style decisions.
Instructions
Read:
spec.mdbehavior.md- The generated code files
doc.mdif it exists
Generate pr.md with this structure:
## <Short imperative title — under 72 chars>
<2–3 sentence summary of what this PR implements and why.>
### Changes
- <Concrete code change 1>
- <Concrete code change 2>
- <Concrete code change 3>
### Decisions (ADR-style)
- <Decision made during behavior step>
→ <The reasoning behind it>
- <Another decision>
→ <The reasoning>
### Acceptance criteria covered
- [x] <Item from spec.md>
- [x] <Item from spec.md>
### Out of scope
- <What this PR deliberately does NOT include>
### Testing
- <Scenarios from behavior.md that are covered>
- <What was tested manually>
Rules
- Title must be imperative voice ("Implement login screen" not "Implemented")
- Title must be under 72 characters
- Every resolved open question from behavior.md becomes a "Decision" entry with its reasoning
- Do not include implementation details that belong in code review comments
After generation
Tell the user: "pr.md is ready. To open the PR directly from terminal:
gh pr create \
--title \"$(head -n1 pr.md | sed 's/^## //')\" \
--body \"$(tail -n +2 pr.md)\"
Run /sage doc to also generate the behavioral reference documentation."
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.
- 4d ago First seen · 69 lines · 13 tokens per session scan A 69560cf35e71
sage-pr is a cursor rule published in the GitHub repository gustavobarbosab/sage (2 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 382 once invoked, about $0.0001 per session on Opus 5. 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.