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 LeekJay/claude-skills-plugin --skill typescript-strict-typinggit clone --depth 1 https://github.com/LeekJay/claude-skills-pluginWrote 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/leekjay/claude-skills-plugin/typescript-strict-typing)<a href="https://agentmods.dev/skills/leekjay/claude-skills-plugin/typescript-strict-typing"><img src="https://agentmods.dev/badge/skills/leekjay/claude-skills-plugin/typescript-strict-typing.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.00092 | $0.02410 |
| Opus 5 | $0.00046 | $0.01205 |
| Sonnet 5 | $0.00018 | $0.00482 |
| Haiku 4.5 | $0.00009 | $0.00241 |
Grade A, and why
typescript-strict-typing 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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Strict Typing Standards
CRITICAL: This skill applies to ALL TypeScript code writing scenarios - not just when fixing type errors.
When to Use This Skill
✅ ALWAYS use when:
- Writing any TypeScript code
- Implementing new features
- Fixing bugs
- Refactoring code
- Modifying existing code
- Adding new functions, classes, or modules
- Working with third-party libraries
- Handling async operations
- Processing data structures
Absolutely Prohibited Patterns
❌ 1. Type Escape Mechanisms
Never use these under any circumstances:
// ❌ WRONG - any type
const data: any = fetchData()
// ❌ WRONG - type assertion
const element = document.getElementById('id') as HTMLInputElement
// ❌ WRONG - double assertion
const value = something as unknown as SomeType
// ❌ WRONG - TypeScript suppression comments
// @ts-ignore
// @ts-expect-error
// ❌ WRONG - ESLint suppression comments for type rules
// eslint-disable-next-line @typescript-eslint/no-explicit-any
// eslint-disable-next-line @typescript-eslint/ban-types
// eslint-disable-next-line @typescript-eslint/no-unsafe-assignment
// eslint-disable-next-line @typescript-eslint/no-unsafe-member-access
// eslint-disable-next-line @typescript-eslint/no-unsafe-call
// eslint-disable-next-line @typescript-eslint/no-unsafe-return
/* eslint-disable @typescript-eslint/no-explicit-any */
// ❌ WRONG - ESLint config files that disable type safety rules
// .eslintrc.js with rules turned off
❌ 2. Non-null Assertion Operator (!)
// ❌ WRONG - non-null assertion
const value = array.find(x => x.id === id)!.name
// ❌ WRONG - property access assertion
const result = obj!.property
// ✅ CORRECT - proper null checking
const item = array.find(x => x.id === id)
if (item) {
const value = item.name
}
❌ 3. Implicit Any
// ❌ WRONG - implicit any parameters
function process(data) {
return data.value
}
// ❌ WRONG - implicit any return
function getData() {
return fetchSomething()
}
// ✅ CORRECT - explicit types
function process(data: DataType): string {
return data.value
}
function getData(): Promise<DataType> {
return fetchSomething()
}
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 · 401 lines · 92 tokens per session scan A 5238f0a906a3
typescript-strict-typing is a skill published in the GitHub repository LeekJay/claude-skills-plugin (4 stars, last pushed 9mo ago), licensed MIT. It adds 92 tokens to every session and 2,410 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
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.
aws-sst-development
SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework.
league-akari-shard-development
Use when creating, extending, refactoring, splitting, or reviewing League Akari main or renderer shards, including shard file organization, controller/loader/executor/handler boundaries, naming conventions, renderer TSX usage, platform guards, and public contract compatibility.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
migrate-better-result-3
Migrate a TypeScript codebase from better-result 2.x to 3.0. Use when upgrading better-result across the TaggedError syntax, removed Result serialization helpers, recovery inference, matching, or retry APIs.