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/rules/gustavobarbosab/sage/sage-code)<a href="https://agentmods.dev/rules/gustavobarbosab/sage/sage-code"><img src="https://agentmods.dev/badge/rules/gustavobarbosab/sage/sage-code/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/rules/gustavobarbosab/sage/sage-code"><img src="https://agentmods.dev/badge/rules/gustavobarbosab/sage/sage-code.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.00013 | $0.00407 |
| Opus 5.5 | $0.00005 | $0.00163 |
| Sonnet 5.5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
sage-code 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 code
Generates production-ready code from spec.md + behavior.md.
Gate check (REQUIRED before generating)
Read behavior.md and check for unresolved open questions (- [ ] items).
If any - [ ] items remain:
⚠️ Cannot generate code — open questions remain in behavior.md:
• <question 1>
• <question 2>
Mark each question resolved with [x] in behavior.md, then run /sage code again.
Stop. Do not generate any code.
Only proceed when all open questions are marked [x] or removed.
Instructions
Read:
- Harness (
.sage/harness.md,CLAUDE.md,.cursorrules, or project knowledge) spec.mdbehavior.md(all resolved scenarios)
Generate production-ready code that:
- Follows harness conventions EXACTLY — stack, naming patterns, architecture, restrictions
- Implements every acceptance criterion from spec.md
- Satisfies every scenario in behavior.md with corresponding test code
- Includes previews/examples where the harness requires them
- Respects every "Do NOT" item from spec.md
Output format
Return files in this format — each file preceded by its path:
// FILE: <relative/path/to/File.kt>
<file content>
// FILE: <relative/path/to/FileTest.kt>
<file content>
Do not include explanations between files unless asked. Do not deviate from the harness architecture.
After generation
Tell the user:
"Code generated. Review it against the acceptance criteria in spec.md — point by point, not by gut feel. Use /sage update <feedback> for any changes needed. When it's ready, run /sage pr and /sage doc to export."
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 · 67 lines · 13 tokens per session scan A aae3d1437213
sage-code is a cursor rule published in the GitHub repository gustavobarbosab/sage (2 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 407 once invoked, about $0.0001 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).