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/nphausg/ai-agent-skills/android_naming_conventionsgit clone --depth 1 https://github.com/nphausg/ai-agent-skillsWrote 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/nphausg/ai-agent-skills/android_naming_conventions)<a href="https://agentmods.dev/rules/nphausg/ai-agent-skills/android_naming_conventions"><img src="https://agentmods.dev/badge/rules/nphausg/ai-agent-skills/android_naming_conventions.svg" alt="Measured on agentmods" 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.00083 | $0.00083 |
| Opus 5 | $0.00042 | $0.00042 |
| Sonnet 5 | $0.00017 | $0.00017 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
android_naming_conventions 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 5d 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
- Classes: PascalCase
- Functions: camelCase
- Constants: UPPER_SNAKE_CASE
- Variables: camelCase
- Test functions: GIVEN_ WHEN THEN
- Avoid abbreviations and cryptic names
- Name should communicate clear intent
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.
- 5d ago First seen · 14 lines · 83 tokens per session scan A f056108175ee
android_naming_conventions is a cursor rule published in the GitHub repository nphausg/ai-agent-skills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 83 tokens to every session, about $0.0004 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
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
type-inference
Derive TypeScript types from Zod schemas - no hand-written interfaces for wire shapes.
paperfit
PaperFit project rule for LaTeX visual typesetting optimization.
cd
GitHub Actions CD - called by release.yml after the tag, no push-tags trigger, Cloudflare versions upload then 100% promote, scoped API token on the production environment, GitHub-owned deployment record.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
guardrails
Hard "don'ts" for every change. When one would be violated, stop and ask rather than proceed.