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 skills/csabakovacs/rulesmith/code-reviewernpx skills add CsabaKovacs/rulesmith --skill code-reviewergit clone --depth 1 https://github.com/CsabaKovacs/rulesmithWhat 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.00029 | $0.00602 |
| Opus 5 | $0.00015 | $0.00301 |
| Sonnet 5 | $0.00006 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
code-reviewer 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Review
Reviews changed files for code quality, convention adherence, and maintainability.
When to Activate
- After ANY code modification that affects application logic, architecture, data flow, or reusable components.
- Skip ONLY for documentation-only, config-only, or trivial text changes.
Review Methodology
Follow these steps in order:
- Identify all changed files and understand the scope of the modification.
- Check adherence to project conventions defined in the rulebook.
- Evaluate naming consistency, readability, and pattern conformance.
- Flag unnecessary complexity, duplication, or DRY violations.
- Verify that changes maintain existing contracts and do not break interfaces.
- Classify findings as critical (must fix), important (should fix), or minor (consider fixing).
- Report ONLY when issues are found — produce no output if the review passes clean.
Stack-Specific Rules
- Enforce strict TypeScript: flag
anytypes, missing return types on exported functions. - Verify
.jsextensions in import paths (NodeNext). (evidence: packages/core/src/index.ts) - Check Zod schemas at boundaries. (evidence: packages/core/src/profile/schema.ts)
- Verify barrel exports. (evidence: packages/core/src/index.ts)
- Check file I/O through
safe.ts. (evidence: packages/core/src/fs/safe.ts) - Module-level functions, no class wrappers. (evidence: packages/core/src/scanner/index.ts)
Project Conventions to Enforce
Architecture
- 3-package monorepo: core, cli, mcp. New features: core → barrel → CLI + MCP. (evidence: pnpm-workspace.yaml)
- Templates in
packs/default/templates/.examples/fixtures/is test data. (evidence: packs/default/)
Code Style
- Constants: UPPER_SNAKE_CASE. Functions: camelCase. Types: PascalCase.
Record<string, unknown>for JSON, neverany. Private helpers unexported.
Execution Guardrails
- Forbidden paths:
.git,node_modules,dist/,vendor/.
Boundaries
- Do NOT automatically apply fixes — report findings for the orchestrator to handle.
- Do NOT review test files unless the change specifically targets test infrastructure.
- Ignore purely stylistic suggestions unless they meaningfully impact maintainability.
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 · 72 lines · 29 tokens per session scan A a9ab4dccb879
code-reviewer is a skill published in the GitHub repository CsabaKovacs/rulesmith (15 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 602 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…