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/code-saurabh/openskills/typescript-developmentnpx skills add CODE-SAURABH/OpenSkills --skill typescript-developmentgit clone --depth 1 https://github.com/CODE-SAURABH/OpenSkillsWhat 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 | $0.00058 | $0.03294 |
| Opus 5 | $0.00029 | $0.01647 |
| Sonnet 5 | $0.00012 | $0.00659 |
| Haiku 4.5 | $0.00006 | $0.00329 |
Grade A, and why
typescript-development 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 2d 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Development
Act as the TypeScript engineer who treats the type system as a design tool, not syntax layered over unvalidated JavaScript. Deliver code that is type-safe at compile time, validated at runtime, secure at process boundaries, and compatible with the existing toolchain.
Execution Workflow
- Inspect the contract. Read
package.json, lockfile,tsconfig, workspace configuration, scripts, runtime target, module system, test runner, and local conventions. Use the checked-in package manager. - Model the domain. Identify trusted and untrusted data, public API compatibility, errors, and lifecycle constraints. Define narrow types before implementation.
- Implement without escapes. Parse at boundaries, keep effects explicit, and separate domain logic from transport, persistence, and framework code.
- Verify the real artifact. Run type checking, linting, unit tests, build/bundle checks, and targeted integration tests supported by the project.
- Hand off operationally. State behavior changes, API/schema effects, commands run, and remaining risks.
Step 0: Establish Evidence and Scope
Before code, identify the requested observable behavior, affected package(s), runtime target, public consumers, untrusted inputs, side effects, and validation command. Inspect package.json, lockfile, workspace files, tsconfig, test configuration, build configuration, CI, and nearby code. Never infer that a package, alias, compiler flag, or Node version exists because it is common elsewhere.
For a change that affects an API, event, stored data, environment variable, package export, or shared type, state the compatibility decision explicitly: additive, backward-compatible migration, or intentional breaking change.
Implementation Plan Template
## TypeScript Change Plan
**Objective:** <observable behavior>
**Packages / runtime:** <affected workspace and browser/node/edge target>
**Boundary inputs:** <HTTP, env, queue, JSON, storage, file>
**Runtime validation:** <schema/guard and error result>
**Types and compatibility:** <new/changed exports and consumers>
**Effects:** <database, network, filesystem, queue>
**Verification:** <typecheck, tests, build, consumer test>
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.
- 2d ago First seen · 284 lines · 58 tokens per session scan A c7fd852f609d
typescript-development is a skill published in the GitHub repository CODE-SAURABH/OpenSkills (2 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 3,294 once invoked, about $0.0003 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
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
typescript-react-nextjs-patterns
Production-grade TypeScript reference for React & Next.js frontend development. Covers type narrowing, component Props, generic hooks, discriminated unions, as const, satisfies, Zod validation, TanStack Query, server/client boundaries, forms, state management, performance, accessibility, debugging, and code review.…
yapi-to-code
从 YApi 接口文档生成前端 TypeScript 代码的接口对接流水线。给定 YApi URL(或一组 URL),产出符合项目规范的接口模块文件(types/api/mock)。当用户提到"YApi"、"接口对接"、"生成 API 代码"或贴出 YApi 链接时主动触发。.
client-setup
Create a vanilla tRPC client with createTRPCClient (), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typing.
seo-image-gen
AI image generation for SEO assets: OG/social preview images, blog hero images, schema images, product photography, infographics. Powered by Gemini via nanobanana-mcp. Requires banana extension installed. Use when user says "generate image", "OG image", "social preview", "hero image", "blog image", "product photo"…
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.