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 tmj-90/gaffer --skill typescript-conventionsgit clone --depth 1 https://github.com/tmj-90/gafferWrote 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/tmj-90/gaffer/typescript-conventions)<a href="https://agentmods.dev/skills/tmj-90/gaffer/typescript-conventions"><img src="https://agentmods.dev/badge/skills/tmj-90/gaffer/typescript-conventions/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/tmj-90/gaffer/typescript-conventions"><img src="https://agentmods.dev/badge/skills/tmj-90/gaffer/typescript-conventions.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.00110 | $0.02197 |
| Opus 5.5 | $0.00044 | $0.00879 |
| Sonnet 5.5 | $0.00022 | $0.00439 |
| Haiku 4.5 | $0.00011 | $0.00220 |
Grade A, and why
typescript-conventions 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 20d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write idiomatic, strict TypeScript
TypeScript protects you only as far as its types are honest: strict mode on, external
data validated rather than cast, and every promise awaited or handled. For the builder and the reviewer of a TS/JS diff; the repo's config and existing code win over it. UI framework patterns live in their own packs (the react-patterns
skill, the frontend packs).
Procedure
- Discover the repo's conventions first. Call
search_lorefor TS conventions. Readtsconfig*.json(strict,noUncheckedIndexedAccess,exactOptionalPropertyTypes,module/moduleResolution,verbatimModuleSyntax,erasableSyntaxOnly), the TypeScript version (6.0 turnedstricton by default and deprecatedbaseUrl,moduleResolution: node; 7.0 removed them and ships the nativetsc),package.json(type,scripts,engines,packageManager), the lockfile that names the package manager (package-lock.jsonnpm,pnpm-lock.yaml,yarn.lock,bun.lock),eslint.config.*orbiome.json, Prettier config, the test runner config, and workspace tooling (turbo.json,nx.json). Copy a sibling module and its test. - Pin the exact commands from
package.jsonscripts and CI (therun-testsandrun-lintskills). Use the defaults below only when the repo defines none. - Write the change with the idioms below, then walk the concurrency section for every promise, shared object, stream, timer, file and outbound call you touched.
- Test each acceptance criterion's own behaviour. One test per AC that fails without
your change, plus its error path. If the AC involves shared state or persistence, add a
test that fires N concurrent requests (
Promise.allover the real handler) and asserts the invariant — Node interleaves at everyawait, so single-threaded code still races. - Verify, then stop. Done when: the type check, lint and format check are clean with
no new suppressions, tests (with the repo's coverage gate) are green, and every AC has
a test. Record the output with the
record-evidenceskill; the runner submits the work.
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.
- 20d ago Changed · +58 lines · +33 tokens per session 08b30aa2b21e
- 22d ago Changed e7de0cb16fa4
- 1mo ago Changed · +55 lines · +61 tokens per session 64861add4de4
- 1mo ago First seen · 12 lines · 16 tokens per session scan A 1cbac80291b8
typescript-conventions is a skill published in the GitHub repository tmj-90/gaffer (2 stars, last pushed 20d ago), licensed Apache-2.0. It adds 110 tokens to every session and 2,197 once invoked, about $0.0004 per session on Opus 5.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
debugging-typescript-errors
Systematically investigates TypeScript compiler errors, traces the real type mismatch, and applies a minimal verified fix. Use when the user wants to debug TypeScript type errors.
sota-javascript-typescript
State-of-the-art JavaScript and TypeScript engineering (2026) for both writing and auditing code. Covers strict TypeScript configuration and type design, language idioms and pitfalls, async patterns, Node.js backends, JS/TS-specific security (XSS, prototype pollution, supply chain, injection), frontend/React and Node…
generics-mastery
Master TypeScript generics for reusable, type-safe abstractions. Use when the user works with generic constraints, conditional types, mapped types, the infer keyword, utility types, recursive types, or needs help building type-safe libraries, APIs, or data structures.
type-patterns
Advanced TypeScript type patterns for modeling complex domains safely. Use when the user needs discriminated unions, branded types, template literal types, type guards, exhaustive checking, const assertions, or is designing type-safe APIs and domain models.
strict-typescript
Enforce strict TypeScript compiler settings and type narrowing patterns. Use when the user creates a new TypeScript project, configures tsconfig.json, encounters null/undefined errors, deals with indexed access issues, or asks about strict mode, type safety, or narrowing techniques.
typescript-expert
TypeScript expert for type system, generics, utility types, and strict mode patterns.