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/dr-code/tessera/code-reviewnpx skills add dr-code/tessera --skill code-reviewgit clone --depth 1 https://github.com/dr-code/tesseraWhat 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.00016 | $0.00553 |
| Opus 5 | $0.00008 | $0.00277 |
| Sonnet 5 | $0.00003 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00055 |
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 yesterday.
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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Skill
When reviewing code, follow this systematic approach:
1. Security (FIRST — always check)
- No hardcoded secrets, API keys, or passwords
- Input validation on all user-provided data
- SQL injection prevention (parameterized queries)
- XSS prevention (sanitized output)
- Authentication/authorization on protected routes
- CORS properly configured
- Rate limiting on public endpoints
2. TypeScript Quality
- No
anytypes (unless documented why) - Explicit return types on public functions
- Null/undefined properly handled (
User | null) - Strict mode enabled
- Enums or union types instead of magic strings
3. Error Handling
- Try/catch around async operations
- Errors logged with context (not swallowed)
- User-facing errors are helpful (not stack traces)
- Unhandled promise rejections caught
4. Performance
- No N+1 database queries
- Proper pagination on list endpoints
- No memory leaks (event listeners cleaned up)
- Database indexes for common queries
- No unnecessary re-renders (React)
5. Testing
- New code has corresponding tests
- Tests have explicit assertions (not just "page loads")
- Edge cases covered (empty, null, max values)
- Mocks are realistic
6. Architecture
- Database access through StrictDB only
- API versioning (/api/v1/) followed
- Service separation respected
- No business logic in route handlers
Output Format
For each issue:
- Severity: 🔴 Critical | 🟡 Warning | 🔵 Suggestion
- Location: file:line
- Issue: What's wrong
- Fix: How to fix it
- Why: Why this matters
RuleCatch Report
After completing the review, check RuleCatch for automated violations:
- If the RuleCatch MCP server is available: query for violations on the reviewed files
- Include results in a dedicated "RuleCatch Violations" section
- This catches pattern-based violations the manual review might miss
- If no MCP: suggest — "Install RuleCatch MCP for automated violation monitoring"
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.
- yesterday First seen · 79 lines · 16 tokens per session scan A 18435fe7ccef
Code Review is a skill published in the GitHub repository dr-code/tessera (1 stars, last pushed 21d ago), licensed MIT. It adds 16 tokens to every session and 553 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…