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/build-tags)<a href="https://agentmods.dev/rules/coddy-project/coddy-agent/build-tags"><img src="https://agentmods.dev/badge/rules/coddy-project/coddy-agent/build-tags/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/build-tags"><img src="https://agentmods.dev/badge/rules/coddy-project/coddy-agent/build-tags.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.00000 | $0.00418 |
| Opus 5.5 | $0.00000 | $0.00167 |
| Sonnet 5.5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
build-tags 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 today.
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
Shipped build tags
The set of build tags that ships (http ui scheduler memory cli gateway swarm metrics today) is not read from one place. A change to it - a tag added, removed or renamed - updates every copy in the same commit:
Makefile,FULL_TAGS(and the examples in its header comment);make testandTEST_TAG_SETSderive from it;Dockerfile,ARG BUILD_TAGS(comma-separated, in its own order);.github/workflows/docker-build-push.yaml,BUILD_TAGS;.github/workflows/release-binaries.yaml,GO_BUILD_TAGS;.github/workflows/tests-on-pr.yaml,PKG_TAGSof the packages job (deliberately withoutui, so the job needs no npm);packaging/homebrew/coddy-formula.rb.tmpl, thetagsarray (the cask installs a built archive and names no tags);make check-windows, which spells its tag combinations by hand;- the build commands in
docs/contributing/build.md,README.mdandAGENTS.md; docs/getting-started/docker.md, the image's default set and its tag list under "What the image contains by default".
A subcommand that reaches the packages for the first time with a new tag also takes the man page and both completions in the same commit (the packaging invariants in AGENTS.md). Check the shipped combination itself, not only each tag alone: make build TAGS="$(FULL_TAGS)", then the packages with the same tags.
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.
- today Changed ad113d07df27
- 7d ago Changed · +2 lines 21e8c56bda13
- 10d ago First seen · 25 lines · 0 tokens per session scan A 56c842961752
build-tags is a cursor rule published in the GitHub repository coddy-project/coddy-agent (175 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 418 tokens. 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-10-06.
Other cursor rules, from other repositories
sciclaw-papercuts
Papercuts from Sol/ImageMagick/release cycles — release, brew, CI, and workspace hygiene for sciClaw agents.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.