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-harness-generate)<a href="https://agentmods.dev/rules/gustavobarbosab/sage/sage-harness-generate"><img src="https://agentmods.dev/badge/rules/gustavobarbosab/sage/sage-harness-generate/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-harness-generate"><img src="https://agentmods.dev/badge/rules/gustavobarbosab/sage/sage-harness-generate.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.00018 | $0.00431 |
| Opus 5 | $0.00009 | $0.00216 |
| Sonnet 5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
sage-harness-generate 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 8d 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 harness generate
Infers .sage/harness.md by analyzing existing codebase files.
Instructions
Ask the user to share files from their codebase. Suggest the most useful ones:
"Please share some files so I can infer your project conventions. The most useful are:
build.gradle.kts/package.json/pyproject.toml(stack and versions)- 2–3 ViewModel or state-holding classes (architecture patterns)
- 2–3 UI files / screens / components (UI conventions)
- 1–2 DI modules (injection approach)
- 1–2 test files (test conventions)
- Any existing
.editorconfig,.cursorrules, orCLAUDE.md"
Once files are provided, analyze them and generate .sage/harness.md:
## Project Harness — <inferred project name>
### Stack
- <inferred stack items with versions>
### Conventions
- <naming patterns with examples from the code>
- <architecture rules>
### Avoid
- <patterns NOT found in the code — things deliberately avoided>
Flags to include
Mark inferences with low confidence:
❓ Possibly: <inferred rule> — confirm before adopting
Mark inconsistencies found across files:
⚠️ Inconsistency: <description> — which version is correct?
Rules
- Only infer what the code actually shows — don't invent conventions
- The "Avoid" section will be sparse on first generation — that's expected
- Always flag ❓ and ⚠️ items for the user to resolve before committing
After generation
Tell the user:
"Harness drafted at .sage/harness.md. Review every ❓ and ⚠️ item before committing. Run /sage harness review after any major refactor to keep it accurate."
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.
- 8d ago First seen · 66 lines · 18 tokens per session scan A c1b6cfa11209
sage-harness-generate is a cursor rule published in the GitHub repository gustavobarbosab/sage (2 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 431 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
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.
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.