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 mfmezger/ai_agent_dotfiles --skill typescript-engineeringgit clone --depth 1 https://github.com/mfmezger/ai_agent_dotfilesWrote 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/mfmezger/ai_agent_dotfiles/typescript-engineering)<a href="https://agentmods.dev/skills/mfmezger/ai_agent_dotfiles/typescript-engineering"><img src="https://agentmods.dev/badge/skills/mfmezger/ai_agent_dotfiles/typescript-engineering/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/mfmezger/ai_agent_dotfiles/typescript-engineering"><img src="https://agentmods.dev/badge/skills/mfmezger/ai_agent_dotfiles/typescript-engineering.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.00122 | $0.00874 |
| Opus 5.5 | $0.00049 | $0.00350 |
| Sonnet 5.5 | $0.00024 | $0.00175 |
| Haiku 4.5 | $0.00012 | $0.00087 |
Grade A, and why
typescript-engineering 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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Engineering
Produce TypeScript that is explicit at boundaries, narrow in surface area, and strict enough that refactors fail fast. Prefer inference inside small scopes, explicit types at module boundaries, runtime validation for external data, and simple control flow over clever type tricks.
Workflow
- Identify the boundary. Library: optimize for stable public types, portability, and narrow exports. Application: optimize for operability, runtime validation, and maintainable module boundaries.
- Model data before behavior. Prefer discriminated unions, branded/domain types, and small interfaces over optional-field soup.
- Decide where trust begins.
Treat network, env, file, CLI, and user input as
unknownuntil validated. - Keep types and implementation aligned. Prefer deriving types from values and functions over duplicating parallel definitions.
- Use async intentionally. Model failure and cancellation explicitly; avoid floating promises and hidden concurrency.
- Verify before finalizing. Run the project’s formatter, linter, type checker, and tests. Treat type errors as design feedback.
Load References By Need
| Need | Reference |
|---|---|
| Project shape, tsconfig, modules, exports, tooling | references/workflow.md |
| Boundary validation, error handling, async and promises | references/runtime-and-errors.md |
| API design, unions, narrowing, generics, utility types | references/types-and-api-design.md |
| React/TSX state, props, hooks, and event typing | references/react-and-tsx.md |
| Testing, mocks, fixtures, snapshots, review checklist | references/testing-and-quality.md |
| Performance, allocation, iteration, and common footguns | references/performance-and-footguns.md |
Default Standards
- Enable strict mode and keep it on.
- Prefer
unknownoveranyat trust boundaries. - Validate external data at runtime before treating it as domain data.
- Prefer discriminated unions over boolean mode flags and optional-field matrices.
- Keep exports intentional. Avoid giant barrel files that hide ownership and increase coupling.
- Return typed domain values from core logic; isolate framework types at the edges.
- Use
Promise<void>andawaitintentionally. Do not leave floating promises. - Prefer stable, readable types over maximally clever conditional-type machinery.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 67 lines · 122 tokens per session scan A 0f8d0f26c3a9
typescript-engineering is a skill published in the GitHub repository mfmezger/ai_agent_dotfiles (7 stars, last pushed 3mo ago), licensed MIT. It adds 122 tokens to every session and 874 once invoked, about $0.0005 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
silo-extension-builder
Help the user design, write, compile, and install a Silo extension from a natural-language description. The extension follows the same format as any publishable Silo extension and can be shared via npm or a tarball URL when ready.
npm-package
Opinionated TypeScript npm package template for ESM packages. Enforces src→dist builds with tsc, strict TypeScript defaults, explicit exports, and publish-safe package metadata. Relative source imports must use .ts or .tsx (never .js); tsc rewrites them via rewriteRelativeImportExtensions. Use this when creating or…
writing-typescript
Idiomatic TypeScript development. Use when writing TypeScript code, Node.js services, React apps, or TypeScript design advice. Emphasizes strict typing, boundary validation, composition, fast feedback, behavior tests, and project-configured tooling. NOT for Go, Python, Rust, plain HTML/CSS/JS, or server-rendered…
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
mainframe-typescript-backend
Design, implement, debug, or review Node.js TypeScript services and Next.js server layers, including APIs, Server Actions, persistence, workers, and backend tests.
javascript-typescript
Professional JavaScript and TypeScript development skill covering modern ES6+, TypeScript, Node.js, Express, React, testing frameworks, and best practices. Use this skill when developing JavaScript/TypeScript applications, building React/Node.js projects, implementing RESTful APIs, or need guidance on modern JS/TS…