Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/kanyun-inc/reskillnpx agentmods add rules/kanyun-inc/reskill/testingWrote 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/kanyun-inc/reskill/testing)<a href="https://agentmods.dev/rules/kanyun-inc/reskill/testing"><img src="https://agentmods.dev/badge/rules/kanyun-inc/reskill/testing/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/kanyun-inc/reskill/testing"><img src="https://agentmods.dev/badge/rules/kanyun-inc/reskill/testing.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.02287 | $0.02287 |
| Opus 5.5 | $0.00915 | $0.00915 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (60 stars, last pushed 28d ago), licensed MIT. It adds 2,287 tokens to every session, about $0.0091 per session on Opus 5.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
tests
Testing requirements — test value bar, TDD workflow, and test writing guidelines.
unit-tests-tdd
TDD for behavior changes; co-located tests; keep touched areas well covered.
every-error-regression-test
Mandatory regression test for every discovered defect or failure (non-negotiable).
testing
Agent engineering standards — Testing (TR-TEST-001, TR-TEST-002, TR-TEST-004, TR-TEST-005, TR-TEST-006, TR-TEST-007).
tdd-patterns
Rigorous Test-Driven Development (TDD) with DUnitX, naming and dependency injection for isolation with fakes and mocks.
android_unit_testing_bdd
Unit testing best practices with BDD style.