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-docgit 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-doc)<a href="https://agentmods.dev/rules/gustavobarbosab/sage/sage-doc"><img src="https://agentmods.dev/badge/rules/gustavobarbosab/sage/sage-doc.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.00367 |
| Opus 5 | $0.00006 | $0.00183 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
sage-doc 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 doc
Generates doc.md — a behavioral reference document for the feature with ADR-style decisions embedded.
Instructions
Read:
spec.mdbehavior.md- The generated code files
pr.mdif it exists
Generate doc.md with this structure:
## <FeatureName> — Behavior Reference
### Supported states
- <State>: <When it occurs — 1 line>
### Validation rules
- <Field>: <Rule and exact trigger condition>
### Edge cases
- <Edge case>: <Expected behavior>
### Decisions
- <Decision made during SAGE workflow>
→ <The reasoning — the WHY, not just the WHAT>
### Out of scope
- <What this feature deliberately does NOT handle>
### Known limitations
- <Current limitation or future improvement>
Rules
- Each item should be 1–2 lines — the goal is a document a teammate scans in 60 seconds
- The "Decisions" section is the most valuable long-term — it captures reasoning that would otherwise be lost
- Every resolved open question from behavior.md must appear as a Decision entry
- Omit empty sections rather than padding with placeholders
- Focus on behavior, not implementation details (those belong in code comments)
After generation
Tell the user: "doc.md is ready. You can publish it to:
- Commit alongside the code in your repo
- Confluence via Atlassian MCP
- Notion via Notion MCP
- Obsidian vault — drop the file in directly
- GitHub Wiki via
gh api"
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 · 64 lines · 13 tokens per session scan A 15582e05ee0a
sage-doc 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 367 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.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.