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/subhansh-dev/agent-maxxing/code-review-checklistnpx skills add subhansh-dev/agent-maxxing --skill code-review-checklistgit clone --depth 1 https://github.com/subhansh-dev/agent-maxxingWhat 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.00024 | $0.00389 |
| Opus 5 | $0.00012 | $0.00195 |
| Sonnet 5 | $0.00005 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
code-review-checklist 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.
What it actually says
Code Review Checklist
Before shipping any code, run through this.
Does It Work?
- Runs without errors
- Handles the happy path
- Handles edge cases (null, empty, 0, negative, very large)
- Handles errors gracefully (try/catch, validation)
- No console.logs or debug code left in
Is It Readable?
- Variable names are descriptive (not
x,temp,data2) - Functions do one thing
- No magic numbers (use constants)
- Comments explain "why", not "what"
- Consistent style with existing codebase
Is It Safe?
- No SQL injection / XSS / path traversal
- No hardcoded credentials
- No secrets in logs or error messages
- Input validation on user-facing endpoints
- Rate limiting on public APIs
Is It Performant?
- No N+1 queries
- No unnecessary re-renders (React)
- No blocking operations on main thread
- Lazy loading for heavy resources
- Pagination for large datasets
Is It Maintainable?
- No code duplication (DRY)
- Clear separation of concerns
- Error messages are helpful
- Configuration is externalized
- Dependencies are pinned
Frontend-Specific
- Accessible (ARIA labels, keyboard nav, contrast)
- Responsive (mobile, tablet, desktop)
- Loading states for async operations
- Error states with recovery paths
- Empty states that guide the user
- No layout shift (CLS)
- 60fps animations (transform + opacity only)
Backend-Specific
- Database migrations are reversible
- API responses are consistent
- Rate limiting is in place
- Logging is sufficient for debugging
- Health check endpoint exists
- Graceful shutdown handling
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 · 68 lines · 24 tokens per session scan A 3589d8fbed50
code-review-checklist is a skill published in the GitHub repository subhansh-dev/agent-maxxing (2 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 389 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
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
fleet-manager
Use when managing, triaging, restarting, escalating, or summarizing Codewhale Pod runs and workers.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
mcp-builder
Design, build, configure, or debug Model Context Protocol servers for codewhale, including stdio and HTTP/SSE transports.
extension-creator
Create, scaffold, customize, validate, and locally test Qwen Code extensions. Use when the user wants a new Qwen Code extension, needs help choosing an extension template, wants to add QWEN.md context, commands, skills, agents, MCP servers, settings, hooks, channels, or LSP servers, or asks how to link and test an…