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/vanessamarely/ai-playbook-repositoWrote 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/vanessamarely/ai-playbook-reposito/style-output)<a href="https://agentmods.dev/rules/vanessamarely/ai-playbook-reposito/style-output"><img src="https://agentmods.dev/badge/rules/vanessamarely/ai-playbook-reposito/style-output/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/vanessamarely/ai-playbook-reposito/style-output"><img src="https://agentmods.dev/badge/rules/vanessamarely/ai-playbook-reposito/style-output.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.00529 | $0.00529 |
| Opus 5 | $0.00264 | $0.00264 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
style-output 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output Style Guidelines
Minimal Diffs
Produce the smallest possible changeset to accomplish the task.
- Modify only the lines necessary to implement the feature or fix.
- Do not reformat unrelated code.
- Do not reorganize imports unless required for the change.
- Do not rename variables or functions outside the scope of the task.
Exception: if the user explicitly requests refactoring or cleanup, broader changes are acceptable.
Path References
All file paths in output must be:
- Relative to the target project root.
- Use forward slashes (
/) regardless of operating system. - Omit leading
./unless semantically required.
Examples: src/components/Button.tsx, tests/unit/api.test.ts, config/database.yml.
No Mass Reformatting
Do NOT apply automatic code formatters (Prettier, Black, gofmt) unless the project has a pre-commit hook configured or the user explicitly requests formatting. Preserve the existing code style of the target file.
No Unrelated Refactors
When fixing a bug or adding a feature:
- Do not extract functions "for cleanliness" unless required.
- Do not split files unless the change demands it.
- Do not introduce design patterns (factory, strategy, etc.) unless solving a concrete problem.
Verification Commands
After proposing changes, suggest commands the user can run to verify correctness:
- Linting:
npm run lint,eslint src/,pylint module/ - Type checking:
tsc --noEmit,mypy . - Tests:
npm test,pytest,mvn test - Build:
npm run build,gradle build,python -m build
Provide the specific command relevant to the project's tooling.
Plan vs. Direct Fix
Plan first for complex changes involving multiple files/modules, architectural decisions, or trade-offs between approaches. Provide: a brief description of the approach, the list of files to modify, and high-level steps — then execute after confirmation.
Fix directly for simple changes: single-file bug fixes, typo corrections, adding a small utility function, updating configuration values.
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.
- 10d ago First seen · 64 lines · 529 tokens per session scan A 834279b22be6
style-output is a cursor rule published in the GitHub repository vanessamarely/ai-playbook-reposito (2 stars, last pushed 1mo ago), licensed MIT. It adds 529 tokens to every session, about $0.0026 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.