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/apexiq/skillsmith/typescript_expertnpx skills add ApexIQ/skillsmith --skill typescript_expertgit clone --depth 1 https://github.com/ApexIQ/skillsmithWrote 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/apexiq/skillsmith/typescript_expert)<a href="https://agentmods.dev/skills/apexiq/skillsmith/typescript_expert"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/typescript_expert.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.1 | $0.00045 | $0.01853 |
| Opus 5 | $0.00023 | $0.00927 |
| Sonnet 5 | $0.00009 | $0.00371 |
| Haiku 4.5 | $0.00005 | $0.00185 |
Grade A, and why
typescript-expert 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 6d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📘 TypeScript Expert — Production-Grade TypeScript
Philosophy: TypeScript's type system is your first line of defense. If it compiles, it should be mostly correct. If you're using
any, you're using JavaScript with extra steps.
1. When to Use This Skill
- Writing new TypeScript/JavaScript modules
- Reviewing TS/JS code for patterns and type safety
- Building React components or Node.js services
- Configuring TypeScript projects (tsconfig, bundlers)
- Migrating JavaScript to TypeScript
- Debugging type errors
2. Type System Mastery
Use Discriminated Unions Over Enums
// GOOD: Discriminated union — exhaustive checking
type Result<T> =
| { status: "success"; data: T }
| { status: "error"; error: string }
| { status: "loading" };
function handleResult(result: Result<User>) {
switch (result.status) {
case "success":
console.log(result.data.name); // TS knows data exists
break;
case "error":
console.error(result.error); // TS knows error exists
break;
case "loading":
showSpinner();
break;
// If you miss a case, TS will warn you
}
}
// BAD: Enum + separate error field — runtime bugs
enum Status { Success, Error, Loading }
interface Result { status: Status; data?: User; error?: string; }
Utility Types
// Don't reinvent — use built-in utility types
type UserCreate = Omit<User, "id" | "createdAt">;
type UserUpdate = Partial<Pick<User, "name" | "email">>;
type ReadonlyUser = Readonly<User>;
type UserRecord = Record<string, User>;
// Branded types for type-safe IDs
type UserId = string & { __brand: "UserId" };
type TeamId = string & { __brand: "TeamId" };
function getUser(id: UserId): User { ... }
// getUser("abc" as TeamId) → Type error!
Zod for Runtime Validation
import { z } from "zod";
const UserSchema = z.object({
name: z.string().min(2).max(100),
email: z.string().email(),
role: z.enum(["member", "admin", "viewer"]).default("member"),
});
type User = z.infer<typeof UserSchema>; // Type derived from schema
// Validate at API boundary
const result = UserSchema.safeParse(requestBody);
if (!result.success) {
return res.status(400).json({ errors: result.error.issues });
}
const user: User = result.data; // Fully typed and validated
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.
- 6d ago First seen · 272 lines · 45 tokens per session scan A 0ad50d0a17ba
typescript-expert is a skill published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 1,853 once invoked, about $0.0002 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
frontend-typescript-rules
Applies React/TypeScript type safety, component design, and state management rules. Use when implementing React components.
angular
Use when building, refactoring, or debugging Angular (v20/21+): standalone components, signals, zoneless change detection, @if/@for/@defer control flow, inject() DI, resource()/httpResource(), RxJS interop, NgRx SignalStore, ng CLI. NOT React (that is react), NOT Next.js (that is nextjs), NOT a TypeScript language…
shared-tooling-biome
Biome v2 unified linter, formatter, and import organizer — single Rust-powered tool replacing ESLint + Prettier with 97% Prettier compatibility and 20x faster performance.
javascript-typescript
JavaScript and TypeScript development with ES6+, Node.js, React, and modern web frameworks. Use for frontend, backend, or full-stack JavaScript/TypeScript projects.
Cursor rules for Next
Cursor rules for Next.js App Router with TanStack Query v5, covering the HydrationBoundary pattern, Server Actions as mutations, and optimistic updates.
Next
Next.js App Router combined with TanStack Query v5 — HydrationBoundary pattern, Server Actions as mutations, optimistic updates, and infinite scroll.