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/Sanmu-27/repo2agentWrote 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/sanmu-27/repo2agent/repo)<a href="https://agentmods.dev/rules/sanmu-27/repo2agent/repo"><img src="https://agentmods.dev/badge/rules/sanmu-27/repo2agent/repo/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/sanmu-27/repo2agent/repo"><img src="https://agentmods.dev/badge/rules/sanmu-27/repo2agent/repo.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.00330 | $0.00330 |
| Opus 5 | $0.00165 | $0.00165 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
repo 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 9d 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
Cursor Repository Rules
This file was generated by repo2agent. It gives AI coding agents the shortest reliable path to work safely in this repository.
Repository Snapshot
- Name: repo2agent
- Stack: Not detected
- Package manager: npm
Project Map
lib/test/docs/examples/.npm-cache/bin/scripts/
Common Commands
- test:
npm run test - lint:
npm run lint
Agent Workflow
- Read the relevant files before editing.
- Prefer existing patterns, naming, and architecture over new abstractions.
- Keep changes scoped to the user request.
- Do not rewrite unrelated code or reformat files outside the change.
- Do not discard local/user changes without explicit permission.
- Update tests when behavior changes.
- Run the smallest meaningful verification command before finalizing.
- In the final response, say what changed, what was verified, and what risk remains.
Safety Rules
- Be careful with secrets, auth, permissions, payments, migrations, generated files, and lockfiles.
- Avoid adding dependencies unless they clearly reduce complexity.
- If a command fails, report the failure and choose the next most useful verification step.
Cursor Notes
- Apply these rules to code edits, reviews, refactors, and generated tests.
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.
- 9d ago First seen · 55 lines · 330 tokens per session scan A 4de23ac0f7f2
repo is a cursor rule published in the GitHub repository Sanmu-27/repo2agent (1 stars, last pushed 4mo ago), licensed MIT. It adds 330 tokens to every session, about $0.0016 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
cursorrules
You are working in a Python 3.12 FastAPI service.
general
Cursor rule "general" from maxgfr/conforme, covering claude.md, project overview, build & test, architecture and keeping docs in sync.
checklist
Before making ANY changes or implementing ANY new features.
nextjs-patterns
// ✅ Correct: Default to Server Components export default async function Page({ params }) { const data = await getData(); return ; }.
testing
testing.
use-bun-instead-of-node-vite-npm-pnpm
../../CLAUDE.md.