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/vinilana/dotcontext/code-reviewnpx skills add vinilana/dotcontext --skill code-reviewgit clone --depth 1 https://github.com/vinilana/dotcontextWhat 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.00012 | $0.01427 |
| Opus 5 | $0.00006 | $0.00714 |
| Sonnet 5 | $0.00002 | $0.00285 |
| Haiku 4.5 | $0.00001 | $0.00143 |
Grade A, and why
Code Review 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Guidelines for reviewing code changes in the @dotcontext/cli project.
When to Use
- Reviewing a pull request or diff
- Validating code during the Review (R) or Validation (V) phases of the PREVC workflow
- Checking a new service, generator, or utility for adherence to project patterns
- Evaluating MCP gateway handler implementations
Project Standards
TypeScript Configuration
- Target: ES2020, Module: CommonJS
- Strict mode enabled (
"strict": true) - Declarations and source maps generated
- Path alias:
@generators/agents/*maps tosrc/generators/agents/*
Code Organization Patterns
Service Layer (22 services in src/services/):
- Each service lives in its own directory under
src/services/ - Exports through
index.tsbarrel files - Constructor takes an options object or required config
- Methods are async where I/O is involved
- Example:
FillService,WorkflowService,AIContextMCPServer
Generators (src/generators/):
- Separate generators for docs, agents, plans, skills
- Accept options objects, return typed result objects (e.g.,
SkillGeneratorResult) - Use frontmatter serialization from
src/types/scaffoldFrontmatter.ts
Utilities (src/utils/):
- Pure functions or thin wrappers:
frontMatter.ts,contentSanitizer.ts,gitService.ts - CLI UI abstraction:
cliUI.tswithCLIInterfacetype - i18n:
i18n.tswithTranslateFntype anden/pt-BRlocale support
MCP Gateway Handlers (src/services/mcp/gateway/):
- One file per gateway:
explore.ts,context.ts,sync.ts, etc. - Exports: handler function, params type, options type, action type
- Uses
createJsonResponse/createErrorResponse/createTextResponsefromresponse.ts - Barrel re-export through
index.tsandgatewayTools.ts
Review Checklist
Architecture
- New code follows the service/generator/util separation
- No direct file I/O in generators -- delegate to services or
fs-extra - MCP handlers do not use
console.log(useprocess.stderr.writefor debug output) -
repoPathis never hardcoded; always resolved through options orgetRepoPath()
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 · 137 lines · 12 tokens per session scan A a5106488c90b
Code Review is a skill published in the GitHub repository vinilana/dotcontext (561 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,427 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.