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 widnyana/eyay-toolkits --skill ts-reviewgit clone --depth 1 https://github.com/widnyana/eyay-toolkitsWrote 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/widnyana/eyay-toolkits/ts-review)<a href="https://agentmods.dev/skills/widnyana/eyay-toolkits/ts-review"><img src="https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/ts-review/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/widnyana/eyay-toolkits/ts-review"><img src="https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/ts-review.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.00099 | $0.00596 |
| Opus 5 | $0.00049 | $0.00298 |
| Sonnet 5 | $0.00020 | $0.00119 |
| Haiku 4.5 | $0.00010 | $0.00060 |
Grade A, and why
ts-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 11d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Review: $ARGUMENTS
Review Checklist
1. Architecture & Patterns
- Clear separation of concerns (routing, business logic, data access)
- Dependency injection or explicit dependencies (no hidden globals)
- Service/module layer handles business logic, not handlers/controllers
- Input validation at the boundary (DTOs, schemas, zod, class-validator)
2. Security
- Auth checks on sensitive endpoints
- Role-based or scope-based access control where needed
- No hardcoded secrets, credentials, or API keys
- Input validation and sanitization on all public inputs
- Parameterized queries (no string interpolation in SQL)
- Webhook signature verification
- No sensitive data in logs or error responses
3. Error Handling
- Errors are properly typed and propagated
- Error messages don't leak internals to clients
- External service calls wrapped in try-catch
- Graceful degradation where appropriate
- No swallowed errors (empty catch blocks)
4. Database
- Transactions for multi-step operations
- Proper indexing for query patterns
- No N+1 queries
- Connection handling (pools, timeouts, cleanup)
5. TypeScript-Specific
- No
anywithout justification - Proper type annotations on public APIs
- Discriminated unions over optional sprawl
- Null/undefined handled explicitly (no implicit
!abuse) - Generics used where they add value, not everywhere
6. Code Quality
- Single responsibility per function/class
- No duplicated logic that should be shared
- Descriptive names (no
data,info,resultas sole identifiers) - No dead code or unreachable branches
- Consistent style with the rest of the codebase
Output Format
Provide:
- Summary: Overall assessment in 1-2 sentences
- Critical Issues: Must fix before merge
- Improvements: Should fix
- Suggestions: Nice to have
- Positive Notes: What's done well
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.
- 11d ago First seen · 70 lines · 99 tokens per session scan A 334b4e6f66be
ts-review is a skill published in the GitHub repository widnyana/eyay-toolkits (7 stars, last pushed 8d ago), licensed MIT. It adds 99 tokens to every session and 596 once invoked, about $0.0005 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
phx-review
Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.
effect-ts
Effect-TS guide for TypeScript, v4 default with v3 support. Use when writing, debugging, or reviewing Effect code across errors, concurrency, services, streams, and schema, or when code imports from 'effect' or any '@effect/' package.
typescript-dev
Full-stack TypeScript with Vite 8, React 19, Tailwind v4, shadcn/ui, Biome, Vitest, and Hono 4. Use when setting up or working in a TypeScript project - components, styling, build and HMR, tests, lint/CI, or a Hono API with type-safe RPC.
solana-kit
Complete guide for @solana/kit - the modern, tree-shakeable, zero-dependency JavaScript SDK from Anza. Covers RPC connections, signers, transaction building with pipe, signing, sending, and account fetching with full TypeScript support.
solana-kit-migration
Helps developers understand when to use @solana/kit vs @solana/web3.js (v1), provides migration guidance, API mappings, and handles edge cases for Solana JavaScript SDK transitions.
react-frontend
React, TypeScript, and Next.js patterns for frontend development. Use when building React components, managing state, fetching data, optimizing performance, or working with Next.js App Router. Covers React 18-19, hooks, Server Components, and type-safe patterns.