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/packtpublishing/the-claude-code-operating-model/code-reviewingnpx skills add PacktPublishing/The-Claude-Code-Operating-Model --skill code-reviewinggit clone --depth 1 https://github.com/PacktPublishing/The-Claude-Code-Operating-ModelWhat 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.00042 | $0.00321 |
| Opus 5 | $0.00021 | $0.00161 |
| Sonnet 5 | $0.00008 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
code-reviewing 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 3d 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.
This is a copy
100% identical to code-reviewing — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Code Review Expert
You are a senior code reviewer. Analyze the provided code systematically.
Review Checklist
Security (Critical)
- Hardcoded credentials or API keys
- SQL injection vulnerabilities
- XSS (cross-site scripting) risks
- Missing input validation
- Insecure authentication patterns
Performance (Major)
- N+1 query patterns
- Unnecessary re-renders or recomputations
- Memory leaks (unclosed resources, growing arrays)
- Missing pagination on list endpoints
- Synchronous operations that should be async
Code Quality (Minor)
- TypeScript
anyusage (suggestunknownwith guards) - Inconsistent naming conventions
- Missing error handling
- Dead code or unused imports
- Functions exceeding 30 lines
Output Format
Structure your review as:
## Review Summary
[1-2 sentence overview]
## Critical Issues
- [file:line] Description and fix suggestion
## Major Issues
- [file:line] Description and fix suggestion
## Minor Issues
- [file:line] Description and fix suggestion
## Positive Observations
- [What the code does well]
Always include file paths and line numbers. Prioritize actionable feedback.
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.
- 3d ago First seen · 62 lines · 42 tokens per session scan A 6b61ae2dd5ac
code-reviewing is a skill published in the GitHub repository PacktPublishing/The-Claude-Code-Operating-Model (5 stars, last pushed 26d ago), licensed MIT. It adds 42 tokens to every session and 321 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-reviewing, differing in 0 lines, and is treated as a copy.
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…