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/tecnomanu/pampaWrote 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/tecnomanu/pampa/code-standards)<a href="https://agentmods.dev/rules/tecnomanu/pampa/code-standards"><img src="https://agentmods.dev/badge/rules/tecnomanu/pampa/code-standards/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/tecnomanu/pampa/code-standards"><img src="https://agentmods.dev/badge/rules/tecnomanu/pampa/code-standards.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.00135 | $0.00135 |
| Opus 5.5 | $0.00054 | $0.00054 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (30 stars, last pushed 1y ago), licensed ISC. It adds 135 tokens to every session, about $0.0005 per session on Opus 5.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
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.
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.
comment_intelligently
Comments should provide context or clarifications that the code alone cannot convey. They are not a substitute for clear code, but a complement to explain why something is done or what external constraints apply.
limit_line_length_for_readability
Keep lines of code short enough to be easily readable and understandable at a glance. Long lines reduce readability, increase cognitive load, and complicate code reviews.