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/coddy-project/coddy-agent/testinggit clone --depth 1 https://github.com/coddy-project/coddy-agentWhat 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 | $0.00776 | $0.00776 |
| Opus 5 | $0.00388 | $0.00388 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
testing 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 yesterday.
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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing (Go)
Commands
- Full suite (what agents should run before finishing):
make test- Runs
go test ./...,-tags=memory,-tags=http,-tags=http,memory,-tags=scheduler,-tags=scheduler,memory, thenmake ui-build, thenhttp,ui,http,ui,memory,http,scheduler,http,scheduler,memory,http,scheduler,ui,http,scheduler,ui,memory(seeMakefiletesttarget).
- Runs
- Targeted run while iterating:
go test ./path/to/pkg -run TestName -count=1 - Touching a file behind
//go:build windows, or any signature it shares with_other.go/ the rest of the tree: also runmake check-windowsandmake lint-windows.make testandmake lintrun on the host, so the Windows half ofinternal/platform(and anything else with a per-OS file) is never compiled by them.check-windowscross-builds andgo vets every non-uitag combination, test files included. CI runs both (.github/workflows/tests-on-pr.yaml), plusgo teston a realwindows-latestrunner forinternal/platform,internal/bgtask, andinternal/tools/shell— the packages whose behavior differs by OS. - HTTP server core is
//go:build http. Embedded UI tests compile withgo test -tags=http,ui ./external/httpserver. SPA-freehttpbuild uses//go:build http && !uihandlers underexternal/httpserver. Session memory REST uses//go:build http && memory(memory_http.go); withoutmemory,memory_http_stub.goregisters no routes.
Conventions
- Prefer table-driven tests where it clarifies cases.
- Keep tests deterministic; avoid real network unless the test is explicitly integration-style and documented.
- New HTTP behavior belongs in
external/httpserver/server_test.go(and related files) with **httpbuild tag parity.
BDD feature specs (features/)
- Happy-path behavior of a feature (and the reproduction of a bug) is an executable Gherkin
spec in the repo-root
features/directory, run by a godog harness (e.g.external/httpserver/bdd_remote_test.go,bdd_workspace_test.go) whoseOptions.Pathspoints at../../features/<name>.feature. - Edge / boundary / error cases are ordinary unit tests next to the code, not scenarios
in
features/. Keep.featurefiles to the correct-behavior story. - Feature suites run under the tag that owns the behavior (e.g.
-tags http) and are part ofmake test. Step definitions may use a stub runner to stay deterministic and LLM-free.
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.
- yesterday First seen · 39 lines · 776 tokens per session scan A 26333c0463dd
testing is a cursor rule published in the GitHub repository coddy-project/coddy-agent (127 stars, last pushed 3d ago), licensed MIT. It adds 776 tokens to every session, about $0.0039 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-30.
Other cursor rules, from other repositories
lean
The smallest working change. Efficiency is not carelessness. Active during delivery in the aiops bundle; off during grill/alignment.
use-bun-instead-of-node-vite-npm-pnpm
../../CLAUDE.md.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.