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/collaborationgit 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.00473 | $0.00473 |
| Opus 5 | $0.00236 | $0.00236 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
collaboration 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Collaboration Preferences
Communication Style
- Be direct and concise, skip unnecessary pleasantries
- When proposing changes, explain the "why" briefly before the "how"
- If uncertain about intent, ask a focused question rather than guessing
Coding Expectations
- Write clean code from the first attempt: no ugly callbacks, no inline logic
- Extract functions, name clearly, single responsibility
- Prefer readability over cleverness
- When refactoring, preserve existing behavior unless explicitly asked to change it
Decision Making
- When multiple approaches exist, briefly present trade-offs and recommend one
- For small decisions, just pick the better option and explain why
- For architectural decisions, switch to Plan mode to discuss
Workflow Preferences
- Don't create files unless absolutely necessary; prefer editing existing ones
- Run tests after meaningful changes to catch regressions early
- When fixing bugs, strictly follow TDD RED-GREEN cycle:
- RED: write a failing test that reproduces the bug, verify it actually fails
- GREEN: write minimal code to make the test pass, verify the fix corresponds to the test
- Never skip the RED step — a test that never failed proves nothing
- After fix: build and run
node dist/cli/index.js <command>to manually verify the actual CLI behavior matches expectations
- Commit only when explicitly asked
- Before creating a commit, always check:
- Changeset: If the change affects public behavior (bug fix / feature / breaking), create a changeset file in
.changeset/following the bilingual format indevelopment.mdc - README: If CLI command behavior, options, or output changed, check if
README.mdneeds updating - Docs: If the change introduces new concepts or modifies architecture, check if
docs/orCLAUDE.mdneed updating
- Changeset: If the change affects public behavior (bug fix / feature / breaking), create a changeset file in
What I Value
- Accuracy over speed: double-check before answering
- Consistency: follow existing patterns in the codebase
- Proactive suggestions: if you notice something off, mention it
- Context awareness: remember what we discussed in this session
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 · 48 lines · 473 tokens per session scan A 599b252f6df7
collaboration is a cursor rule published in the GitHub repository kanyun-inc/reskill (59 stars, last pushed 21d ago), licensed MIT. It adds 473 tokens to every session, about $0.0024 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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.