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/typefox/agent-skills/ts-code-reviewernpx skills add TypeFox/agent-skills --skill ts-code-reviewergit clone --depth 1 https://github.com/TypeFox/agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/typefox/agent-skills/ts-code-reviewer)<a href="https://agentmods.dev/skills/typefox/agent-skills/ts-code-reviewer"><img src="https://agentmods.dev/badge/skills/typefox/agent-skills/ts-code-reviewer.svg" alt="Measured on agentmods" height="20"></a>What 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.00082 | $0.01627 |
| Opus 5 | $0.00041 | $0.00813 |
| Sonnet 5 | $0.00016 | $0.00325 |
| Haiku 4.5 | $0.00008 | $0.00163 |
Grade A, and why
ts-code-reviewer 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 4d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Code Review
Produce a thorough, actionable code review of TypeScript/JavaScript code at the level of a principal engineer. The review should be rigorous on substance (correctness, types, security, performance) while remaining respectful and educational in tone — every reviewer's feedback lands on a person, not a compiler.
Workflow
Follow these steps in order:
-
Gather the code. Identify what is being reviewed — a file, a diff, a PR, pasted snippets. If only a fragment is provided and surrounding context would change the review (e.g. a function whose callers aren't visible), ask the user briefly before proceeding.
-
Confirm the output location. Ask the user where to write the review file. Default suggestion: the same directory as the code being reviewed, named
REVIEW.md. Do not write the file until the location is confirmed. A short question like "I'll write the review to<path>/REVIEW.md— does that work, or would you prefer somewhere else?" is enough. -
Analyze. Walk the code against the dimensions in the Analysis framework below. Do not include this analysis in the output — it is internal scaffolding to form the review.
-
Write the review to the confirmed path using the structure in Output format. All feedback items must use Conventional Comments notation (see
conventional-comments.md). -
Surface the file to the user with a short summary of the verdict and the top 1–3 priorities. Do not restate the whole review in chat — the file is the deliverable.
Review philosophy
These principles shape how feedback is written. They matter because a review that is technically correct but tonally off will be ignored or resented, and a review that is gentle but vague will not improve the code.
- Assume good intent. The author made reasonable choices given context you may not have. Seek to understand before critiquing.
- Be specific and actionable. Vague feedback wastes everyone's time. Every issue gets a clear path to resolution — usually a concrete code suggestion.
- Balance criticism with praise. Acknowledge what is done well. Good review is mentorship, not gatekeeping. Include at least one
praise:when the code earns it. - Prioritize ruthlessly. Not everything matters equally. Distinguish blocking issues from polish.
- Teach, don't just correct. Explain the why so the author learns the principle, not just the fix.
- Prefer questions over accusations when uncertain. If you don't know whether something is a bug or intentional, use
question:rather thanissue:.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 153 lines · 82 tokens per session scan A 30012c10eb19
ts-code-reviewer is a skill published in the GitHub repository TypeFox/agent-skills (5 stars, last pushed 5d ago), licensed MIT. It adds 82 tokens to every session and 1,627 once invoked, about $0.0004 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
integrated-browser
Use this when working on the VS Code integrated browser ("browserView") to understand its architecture and mental model. Covers the embedded Chromium browser, its editor tab, navigation, overlay/layout, sessions, and agent browser tools under src/vs/platform/browserView and src/vs/workbench/contrib/browserView.
agent-host-e2e-tests
Use when writing, recording, updating, validating, or troubleshooting the agent host end-to-end tests under src/vs/platform/agentHost/test/node/e2e (black-box tests that drive the whole agent host over the AHP protocol, using a CapiReplayProxy record/replay system for Claude/Copilot/Codex). Covers adding a…
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…
analyze-market
Perform a market analysis for a product category or segment. Trigger on: market analysis, market size, TAM SAM SOM, market opportunity, industry analysis.