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/config-roundtrip)<a href="https://agentmods.dev/rules/coddy-project/coddy-agent/config-roundtrip"><img src="https://agentmods.dev/badge/rules/coddy-project/coddy-agent/config-roundtrip/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/config-roundtrip"><img src="https://agentmods.dev/badge/rules/coddy-project/coddy-agent/config-roundtrip.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.00207 |
| Opus 5.5 | $0.00000 | $0.00083 |
| Sonnet 5.5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
config-roundtrip 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 11d 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
Configuration round trips
- Use shared source loading for BOM and CRLF or CR normalization, and preserve the source line-ending convention on write.
- Relocate yaml.v3 syntax lines with bounded prefix parsing instead of trusting the raw parser line blindly.
- A PUT compares against the exact client revision and restores only untouched fields.
- When the source is missing, write one complete valid configuration; never restore defaults over the request.
- Restore write-only secrets from live state. Redaction placeholders must never overwrite stored values.
- Map fields use a three-way key merge for concurrent additions and removals.
- A successful save updates the SPA cache immediately. Stale reads cannot replace it; untouched forms may adopt refreshed copies, while edited forms wait for Reload.
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.
- 11d ago First seen · 19 lines · 0 tokens per session scan A 20299579bec5
config-roundtrip 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 207 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-05.
Other cursor rules, from other repositories
create-ticket
../../.claude/skills/create-ticket/SKILL.md.
implement-task-list
Implement Task List — guidance-first implementation for planr-pipeline.
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.