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/kanyun-inc/reskill/testinggit clone --depth 1 https://github.com/kanyun-inc/reskillWhat 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.02287 | $0.02287 |
| Opus 5 | $0.01144 | $0.01144 |
| Sonnet 5 | $0.00457 | $0.00457 |
| Haiku 4.5 | $0.00229 | $0.00229 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Rules
Testing Philosophy
reskill uses a two-layer testing strategy to ensure code quality and functionality:
| Test Type | Purpose | Frequency |
|---|---|---|
| Unit Tests | Ensure code quality and logic correctness | Run continuously during development |
| Integration Tests | Ensure CLI API usability | Must pass before commit |
Core Principle: Integration tests are the ultimate guarantee of functionality. Unit tests may all pass, but if integration tests fail, users will encounter issues in actual use.
Spec-Driven TDD Workflow
All CLI feature development must follow the Spec-Driven TDD workflow (see docs/cli-spec.md):
┌─────────────────────────────────────────────────────────────────┐
│ 1. SPEC Modify docs/cli-spec.md to define expected behavior│
│ 2. REVIEW Review spec changes │
│ 3. TEST Write failing tests based on spec (RED) │
│ 4. CODE Write minimal code to pass tests (GREEN) │
│ 5. REFACTOR Refactor and optimize, keep tests passing │
│ 6. VERIFY pnpm test:run && pnpm test:integration │
└─────────────────────────────────────────────────────────────────┘
Benefits of Test-First Approach
| Benefit | Description |
|---|---|
| Spec as Documentation | docs/cli-spec.md is the single source of truth for command behavior |
| Tests as Specification | Test code verifies correct implementation of spec |
| Prevent Regression | Any breaking changes will be caught by tests |
| Design-Driven | Think about interfaces first, then implement details |
Example: Adding --dry-run Option
# Step 1: Modify docs/cli-spec.md, add --dry-run option definition
# Step 2: PR Review spec changes
# Step 3: Write failing tests
# - src/cli/commands/__integration__/install-*.test.ts (integration)
# - src/cli/commands/install.test.ts (unit)
# Step 4: Implement --dry-run logic
# Step 5: Refactor code
# Step 6: Verify all tests pass
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 First seen · 352 lines · 2,287 tokens per session scan A e4e7d364b828
testing is a cursor rule published in the GitHub repository kanyun-inc/reskill (59 stars, last pushed 21d ago), licensed MIT. It adds 2,287 tokens to every session, about $0.0114 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
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.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.