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/kevinslin/skillz/derived-cursor-rulesgit clone --depth 1 https://github.com/kevinslin/skillzWhat 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.01368 |
| Opus 5 | $0.00000 | $0.00684 |
| Sonnet 5 | $0.00000 | $0.00274 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
derived-cursor-rules 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Headers
This document defines the rules, coding standards, workflow guidelines, references, documentation structures, and best practices for the AI coding assistant. It is a living document and will be updated as needed.
TECH STACK
(Add details of the tech stack being used, including languages, frameworks, libraries, and tools.)
PROJECT DOCUMENTATION & CONTEXT SYSTEM
(Describe how project documentation is structured and accessed by the AI assistant. Include details about file naming conventions, locations, and the tools used to manage documentation.)
- New files should be named with a
DESIGN-combined.mdformat when combining design documents.
CODING STANDARDS
(Define the coding standards to be followed, including naming conventions, code formatting, commenting, and error handling.)
WORKFLOW & RELEASE RULES
(Describe the project workflow, including branching strategies, code review processes, testing procedures, and release management.)
- After running
npm run buildto create./dist/cli.js, execute the CLI using eithernode ./dist/cli.js …directly. Alternatively, after runningnpm link(or installing the package), the CLI can be called directly usingskillz …. - The
skillz listcommand should, by default, provide a concise output, displaying each skill as a markdown bullet point with its name and the first 100 characters of its description. The description should have whitespace normalized, be trimmed, and have an ellipsis appended if truncated. If no description is available, the output should display "No description provided".
DEBUGGING
(Specify debugging strategies and tools. Detail how the AI assistant should approach debugging tasks.)
- When encountering ESLint errors related to
tsconfig.jsoninclusion, consider creating a separatetsconfig.eslint.jsonthat includes test files. This allows for type-aware linting in tests without affecting the main build configuration. Thetsconfig.eslint.jsonshould:- Extend the main
tsconfig.json. - Set
"noEmit": true. - Set
"rootDir": ".". - Include source and test files in the
"include"array (e.g.,"include": ["src/**/*.ts", "tests/**/*.ts"]). - Exclude
node_modulesanddistdirectories in the"exclude"array (e.g.,"exclude": ["node_modules", "dist"]).
- Extend the main
- Ensure ESLint configuration (
.eslintrc.cjs) uses the correcttsconfig.eslint.jsonfor parser options:
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 · 80 lines · 1,368 tokens per session scan A 5ee52b9b5b9b
derived-cursor-rules is a cursor rule published in the GitHub repository kevinslin/skillz (9 stars, last pushed 22d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,368 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-31.
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.