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/0xnyk/awesome-agent-cortex/testinggit clone --depth 1 https://github.com/0xNyk/awesome-agent-cortexWhat 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.00000 | $0.00132 |
| Opus 5 | $0.00000 | $0.00066 |
| Sonnet 5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
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.
What it actually says
- Write tests before or alongside implementation
- Structure: Arrange-Act-Assert (Given-When-Then)
- Name tests descriptively: test_
- Each test should be independent — no shared mutable state
- Mock external dependencies, not internal logic
- Cover edge cases: empty inputs, boundary values, errors
- Target 80%+ coverage; 100% for critical paths
- Keep test files colocated with source or in parallel test directory
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 · 14 lines · 132 tokens per session scan A 2bddff0afd85
testing is a cursor rule published in the GitHub repository 0xNyk/awesome-agent-cortex (209 stars, last pushed 4d ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 132 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-08-30.
Other cursor rules, from other repositories
langchain
LangChain: chains, agents, memory, tools.
aria-audit
ARIA audit skills — /audit dispatcher plus /audit-knowledge, /audit-config, /audit-style, /audit-usage. Use when user says 'audit knowledge', 'audit config', 'audit style', 'audit usage', 'review setup', or runs the slash commands.
aria-context
ARIA context surfacing — /context and /rules. Use whenever the user asks to load knowledge by topic, references a tag, or asks 'what do we know about X' or 'look up rule N'. Also fires the implicit task-start tag match described in AGENTS.md.
aria-rule-22
Rule 22 — change decision framework. Apply BEFORE every Edit/Write: emit a [Rule 22] block (Low Impact or High Impact 7-step) ABOVE the tool call in the same turn, then run scripts/aria/record-edit-intent.sh to log intent. Verify scope AFTER each edit.
aria-core
ARIA core — five-phase knowledge lifecycle (capture → govern → promote → apply → refresh), knowledge taxonomy, ideas backlog routing, project tier. Consulted whenever ARIA behavior is in question.
010-documentation-context
Require using Context7 or Web Search to review library documentation before implementation.