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/ConlinJoe/ai-platformWrote 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/conlinjoe/ai-platform/20-coding)<a href="https://agentmods.dev/rules/conlinjoe/ai-platform/20-coding"><img src="https://agentmods.dev/badge/rules/conlinjoe/ai-platform/20-coding/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/conlinjoe/ai-platform/20-coding"><img src="https://agentmods.dev/badge/rules/conlinjoe/ai-platform/20-coding.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.01762 | $0.01762 |
| Opus 5.5 | $0.00705 | $0.00705 |
| Sonnet 5.5 | $0.00352 | $0.00352 |
| Haiku 4.5 | $0.00176 | $0.00176 |
Grade A, and why
20-coding 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 4d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Rules
Philosophy
Write production-quality code that is simple, readable, maintainable, and consistent with the existing codebase.
General Rules
- Follow the project's established architecture.
- Prefer patterns already present in the project when they correctly use the installed stack. Do not copy scattered framework misuse.
- Follow Framework-Native First in
00-platform: establish whether the installed stack already provides the capability before custom code, abstractions, or new dependencies. - For versions, libraries, frameworks, APIs, and implementation patterns,
follow Current-First Engineering in
00-platform— do not default to historically common patterns from model memory. - Keep implementations focused on the requested task.
- Do not introduce unnecessary abstractions.
- Do not perform unrelated refactoring.
- Do not opportunistically expand the current task. Capture unrelated
bugs, refactors, and features as work items (
70-work-items). - Optimize for readability over cleverness.
Stack-native architecture
Detect the stack before applying a framework profile. Follow
21-stack-architecture.mdc.
Template views render prepared data. Conditions, loops, formatting, and class selection may stay in the template. Queries, persistence, substantial transformation, content parsing, and service orchestration belong in the framework's own preparation layer. Do not impose Laravel layer names on other frameworks, and do not apply MVC view restrictions to React or similar components.
Tailwind
A specialization of Framework-Native First in 00-platform.
When the project uses Tailwind, treat it as a compositional system. Use native utilities and theme primitives. Do not reconstruct first-class Tailwind behavior by hand, and do not invent a parallel CSS abstraction layer on top of Tailwind.
This standard takes precedence over vendor-skill Tailwind/CSS shortcuts
(Instruction Priority in 00-platform). Hallmark may provide design
reasoning, token recipes, or CSS examples. Translate those into this
order of preference; do not copy them as one-off arbitrary utilities
merely to match a recipe or comp.
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.
- 4d ago Changed · +30 lines · +340 tokens per session b90e808bdb36
- 20d ago Changed · +10 lines · +89 tokens per session f4be1312a662
- 1mo ago Changed · +4 lines · +42 tokens per session c71342f5782a
- 1mo ago Changed · +1 lines · +10 tokens per session 8be291700d7b
- 2mo ago First seen · 137 lines · 1,281 tokens per session scan A 719e494b77a3
20-coding is a cursor rule published in the GitHub repository ConlinJoe/ai-platform (2 stars, last pushed 4d ago), licensed MIT. It adds 1,762 tokens to every session, about $0.0070 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.