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/wellapp-ai/well/code-reviewnpx skills add WellApp-ai/Well --skill code-reviewgit clone --depth 1 https://github.com/WellApp-ai/WellWhat 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.00011 | $0.00517 |
| Opus 5 | $0.00005 | $0.00259 |
| Sonnet 5 | $0.00002 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
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 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.
What it actually says
Code Review Skill
Systematically review code for quality, conventions, and potential issues.
When to Use
- Before committing changes (auto-triggered)
- Reviewing others' PRs
- Self-review before pushing
- Pre-push validation (Phase 0)
Phase 0: Pre-Push Validation
Before reviewing code, ensure build passes:
-
npm run typecheck- No type errors -
npm run lint- No lint errors - No console.log in changed files
- Tests pass (if applicable):
npm run test
If any check fails, fix before proceeding to code review.
Quick check command:
npm run typecheck && npm run lint
Check for console.log:
git diff --cached --name-only | xargs grep -l "console.log" 2>/dev/null
Review Checklist
Hard Rules Check
- No
anytype usage - No console.log statements
- Components under 200 lines
- No inline styles (Tailwind only)
- No arbitrary values (
px-[13px]) - API follows 3-layer pattern
Code Quality Check
- Clear variable/function names
- No duplicated code
- Proper error handling
- Types are specific (not
unknowneverywhere)
Conventions Check
- Follows existing patterns in codebase
- Imports organized correctly
- File in correct location (feature folder)
Security Check
- No hardcoded secrets/API keys
- No exposed sensitive data
- Proper input validation
Output Format
Present findings as:
Code Review Summary
Files Changed: [count] Issues Found: [count by severity]
Critical (must fix)
-
file.ts:L42- [issue description]
Warnings (should fix)
-
file.ts:L15- [issue description]
Suggestions (nice to have)
-
file.ts:L88- [suggestion]
Approved
- No blocking issues found
Proceed with commit? (yes / fix issues first)
Auto-Trigger
This skill is automatically invoked before every commit.
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 · 98 lines · 11 tokens per session scan A 2127b0c97dc8
code-review is a skill published in the GitHub repository WellApp-ai/Well (340 stars, last pushed 26d ago), licensed MIT. It adds 11 tokens to every session and 517 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
auto-reader-ocr
Extract text from images/PDFs (Arabic-first, manga-aware Japanese, 13+ languages auto-detected), translate between 100+ languages, and pull structured fields from invoices/receipts/IDs via the Auto-Reader OCR API. Use when the user shares a document image or PDF to read, translate, or extract data from — or asks for…
server-setup
Initialize tRPC with initTRPC.create(), define routers with t.router(), create procedures with .query()/.mutation()/.subscription(), configure context with createContext(), export AppRouter type, merge routers with t.mergeRouters(), lazy-load routers with lazy().
client-setup
Create a vanilla tRPC client with createTRPCClient (), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typing.
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).
caching
Set HTTP cache headers on tRPC query responses via responseMeta callback for CDN and browser caching. Configure Cache-Control, s-maxage, stale-while-revalidate. Handle caching with batching and authenticated requests. Avoid caching mutations, errors, and authenticated responses.
portaljs-connect-ckan
Wire a scaffolded PortalJS portal to a CKAN backend over its API. Generates a tiny server-side fetch client (no runtime dependency) and feeds the /search catalog and /@namespace/slug showcases from CKAN instead of datasets.json. Use when connecting an existing portal to a live CKAN instance instead of a static…