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/zackiles/cursor-config/with-repomixgit clone --depth 1 https://github.com/zackiles/cursor-configWhat 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.00000 | $0.00526 |
| Opus 5 | $0.00000 | $0.00263 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
with-repomix 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 2d 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL: This Codebase Has A Repomix Snapshot
Do NOT use your tools to search the codebase or read files for this turn. Instead do the following:
- The file snapshot.xml contains a snapshot of the entire codebase with all its code files and documentation
- You can use snapshot.xml to understand the codebase at a high-level.
- Read all or parts of snapshot.xml to find the files or code you're looking for before trying to read the actual file
- You can grep search this file, or read individual lines
- It is a parsed AST of the codebase and contains almost all file names, classes, methods, imports, exports, code comments, variables, constants...
- Grep search for the same terms you would when using your codebase search tool
- Highly granular parts of the code are not shown in snapshot.xml, and require you to review the actual file
- NOTE: Fallback on your regular tools if you can't find what you're looking for in snapshot.xml or the file seems inaccurate or out-of-date.
Reading And Generating The Snapshot
- REPOMIX FILE LOCATION: Stored in snapshot.xml
- REPOMIX FILE CONTENTS: Contains code, documentation, and tests related to this project condensed into a single file
- The repomix configuration is at repomix.config.json
- You can update the snapshot when needed by running the script at build-snapshot.sh
- IMPORTANT: Use the file
codebase-summary.xmlONLY as a reference. Prefer to inspect the actual files in the codebase if you need granularity on a specific piece of code
When Adding or Removing Files To This Codebase
- Update the Repomix config at repomix.config.json so that they're tracked or untracked in the snapshot (if they aren't already)
- To track a file add the glob pattern to the
includearray like so:
{
"include": ["README.md", "src/**/*.ts", "test/**/*.ts", "docs/**/*.md"]
}
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.
- 2d ago First seen · 35 lines · 0 tokens per session scan A 307cf2adca78
with-repomix is a cursor rule published in the GitHub repository zackiles/cursor-config (17 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 526 tokens. 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-30.
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.