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/coddy-project/coddy-agentWrote 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/coddy-project/coddy-agent/code-style)<a href="https://agentmods.dev/rules/coddy-project/coddy-agent/code-style"><img src="https://agentmods.dev/badge/rules/coddy-project/coddy-agent/code-style/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/coddy-project/coddy-agent/code-style"><img src="https://agentmods.dev/badge/rules/coddy-project/coddy-agent/code-style.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.00260 | $0.00260 |
| Opus 5.5 | $0.00104 | $0.00104 |
| Sonnet 5.5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
code-style 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
Code style (Go)
gofmt/go fmt- format before committing when you touch files.make lint- the repo gate (seeMakefile):make fmt-check(gofmt -s -lover every Go file git tracks, whatever its build tags or platform),golangci-lintover the untagged tree, over every tag butuiand over the shipped tag set, thentsc --noEmitover the SPA sources (make ui-typecheck)..golangci.ymlenables thegofmtformatter (gofmt -s) beside the five linters it names (golangci-lint'sstandardset), so an unformatted file fails the gate;gofmt -s -w <file>orgolangci-lint fmtfixes it.- Comments in code - English only.
- Follow existing patterns in neighboring files (imports grouping, naming, error handling).
References
@Makefile
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 Changed · +103 tokens per session bb036e99ebfc
- 11d ago Changed 6bf8a7cb6c56
- 27d ago Changed · +34 tokens per session 39a3da06bbca
- 1mo ago First seen · 17 lines · 123 tokens per session scan A 25e575e8ee8b
code-style is a cursor rule published in the GitHub repository coddy-project/coddy-agent (175 stars, last pushed yesterday), licensed MIT. It adds 260 tokens to every session, about $0.0010 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
helix
Act as expert senior Golang/Python engineer.
go-api-handlers
Use authorization functions for apps.
1004-golang
APPLY Go best practices WHEN writing Go code TO ensure clean, efficient, and maintainable programs.
go
Go patterns: error wrapping, goroutines, interfaces.
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.