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/tecnomanu/pampa/code-standardsgit clone --depth 1 https://github.com/tecnomanu/pampaWhat 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.00135 | $0.00135 |
| Opus 5 | $0.00068 | $0.00068 |
| Sonnet 5 | $0.00027 | $0.00027 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
code-standards 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.
What it actually says
Global Code Standards
- Follow consistent code formatting across the entire project.
- Use meaningful variable and function names that explain their purpose.
- Keep functions small and focused on a single responsibility.
- Add meaningful comments for complex logic, but avoid obvious comments.
- Remove debug code, commented-out code and console logs before committing.
- Use proper indentation (spaces or tabs) consistently throughout the project.
- Follow the language/framework's standard style guide.
- Avoid deep nesting of conditionals and loops.
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 · 17 lines · 135 tokens per session scan A 75a6a9bb5b94
code-standards is a cursor rule published in the GitHub repository tecnomanu/pampa (29 stars, last pushed 11mo ago), licensed ISC. It adds 135 tokens to every session, about $0.0007 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-30.
Other cursor rules, from other repositories
cursor-behavior-constraints
Constraints on how Cursor should behave when designing and implementing UX, UI, IA, and accessibility patterns.
design-core
Balanced always-on core of UX, UI, IA, and accessibility principles for every interaction.
enterprise-ia-patterns
Use for complex, multi-product or multi-tenant IA. Covers cross-product navigation, deep hierarchies, account/org structures, and wayfinding at scale.
ia-navigation-and-structure
Information architecture patterns for navigation, structure, and labeling.
group_what_shares_common_meaning
Methods should group only lines of code that share a common intention. Different responsibilities must be extracted into separate methods or services.
method_naming_should_reflect_intention
Method names must clearly communicate the action or intention of the method. The level of detail should correspond to the method’s position in the execution chain.