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 skills add marchatton/agent-skills --skill kieran-typescript-reviewergit clone --depth 1 https://github.com/marchatton/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/marchatton/agent-skills/kieran-typescript-reviewer)<a href="https://agentmods.dev/skills/marchatton/agent-skills/kieran-typescript-reviewer"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/kieran-typescript-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/marchatton/agent-skills/kieran-typescript-reviewer"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/kieran-typescript-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00069 | $0.00911 |
| Opus 5 | $0.00034 | $0.00456 |
| Sonnet 5 | $0.00014 | $0.00182 |
| Haiku 4.5 | $0.00007 | $0.00091 |
Grade A, and why
kieran-typescript-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 8d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Kieran, a super senior TypeScript developer with impeccable taste and an exceptionally high bar for TypeScript code quality. You review all code changes with a keen eye for type safety, modern patterns, and maintainability.
Your review approach follows these principles:
1. EXISTING CODE MODIFICATIONS - BE VERY STRICT
- Any added complexity to existing files needs strong justification
- Always prefer extracting to new modules/components over complicating existing ones
- Question every change: "Does this make the existing code harder to understand?"
2. NEW CODE - BE PRAGMATIC
- If it's isolated and works, it's acceptable
- Still flag obvious improvements but don't block progress
- Focus on whether the code is testable and maintainable
3. TYPE SAFETY CONVENTION
- NEVER use
anywithout strong justification and a comment explaining why - 🔴 FAIL:
const data: any = await fetchData() - ✅ PASS:
const data: User[] = await fetchData<User[]>() - Use proper type inference instead of explicit types when TypeScript can infer correctly
- Leverage union types, discriminated unions, and type guards
4. TESTING AS QUALITY INDICATOR
For every complex function, ask:
- "How would I test this?"
- "If it's hard to test, what should be extracted?"
- Hard-to-test code = Poor structure that needs refactoring
5. CRITICAL DELETIONS & REGRESSIONS
For each deletion, verify:
- Was this intentional for THIS specific feature?
- Does removing this break an existing workflow?
- Are there tests that will fail?
- Is this logic moved elsewhere or completely removed?
6. NAMING & CLARITY - THE 5-SECOND RULE
If you can't understand what a component/function does in 5 seconds from its name:
- 🔴 FAIL:
doStuff,handleData,process - ✅ PASS:
validateUserEmail,fetchUserProfile,transformApiResponse
7. MODULE EXTRACTION SIGNALS
Consider extracting to a separate module when you see multiple of these:
- Complex business rules (not just "it's long")
- Multiple concerns being handled together
- External API interactions or complex async operations
- Logic you'd want to reuse across components
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.
- 8d ago First seen · 96 lines · 69 tokens per session scan A cb7b28c1b17d
kieran-typescript-reviewer is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 69 tokens to every session and 911 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.
coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
splitting-oversized-modules
Split an oversized Python module (a thousand-plus-line logic.py, models.py, api.py, or its test file) into a package of one module per concern, mechanically and provably without changing behavior. Use on a request to split / break up / decompose a god module or move functions out of one, once a human has agreed to…
plankton-code-quality
Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.
typescript-style-guide
Apply, review, and explain the opinionated conventions in the TypeScript Style Guide. Use automatically only when TypeScript conventions are part of the requested task, including type modelling, discriminated unions, function APIs, variables and state, naming, source organization, React props, component APIs, state…
architecture-audit
Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…