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 wahidyankf/ose-public --skill programming-typescriptgit clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/programming-typescript)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/programming-typescript"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/programming-typescript/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/wahidyankf/ose-public/programming-typescript"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/programming-typescript.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.00045 | $0.00933 |
| Opus 5.5 | $0.00018 | $0.00373 |
| Sonnet 5.5 | $0.00009 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
programming-typescript 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Programming TypeScript
TypeScript Standards owns every TypeScript rule, strict typing included. This skill restates none of them. It carries the procedure for applying that standard, and the judgement of noticing which rule a decision falls under. developing-applications covers the language-agnostic judgement, and Red, Green, Refactor owns the test-first cycle.
Before the First Edit
- Read the standard. Read TypeScript Standards in full, plus React Standards or Next.js Standards when the code uses them.
- Compare the project's configuration with it. A relaxed compiler option or a lint rule switched off is a finding to raise, not a baseline to copy into new code.
- Read the tests that cover the code before interpreting or changing it.
- List the increments, each one observable behaviour, simplest first, including every expected failure path.
Drive Each Increment Test-First
Run each increment through Red, Green, Refactor at the narrowest target that can prove it, usually a unit test with its operating-system-facing dependencies injected. Run the type check as part of each green, not only at the end: a type error discovered after several cycles tends to force a redesign of work already written.
When the compiler rejects a change, fix the code. The standard lists what never silences a type error, and reaching for one of those means the design, not the checker, needs attention.
Notice Which Rule Applies
These moments recur. Each points at the part of the standard that decides it:
| While writing, you meet | Apply, in TypeScript Standards |
|---|---|
| data arriving from a request, file, storage, or the environment | Typing Rules, on validation |
| a value whose shape is not known yet | Typing Rules, on any |
| two flags or optional fields that must never be set together | Typing Rules, on unions |
| two identifiers or quantities of the same primitive that must not mix | Typing Rules, on branded types |
| a call that can fail during normal operation | Expected Failures Are Returned |
| a promise started without being awaited or returned | Expected Failures Are Returned |
| a business decision taking shape inside an effectful function | Typing Rules, on code shape |
What ships with it
1 file 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.
- 2d ago First seen · 70 lines · 45 tokens per session scan A 057378e957a3
programming-typescript is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 933 once invoked, about $0.0002 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-10-14.
Other skills, from other repositories
typescript-test-writing
Use this skill when writing or modifying tests in the llxprt-code repository. Covers mandatory TDD, behavioral testing, bun:test conventions and file naming, mock hygiene (no mock theater), and what never to test. Distilled from dev-docs/RULES.md, which remains the source of truth.
typescript-eval
Test TypeScript code snippets before persisting as skills.
Unit Test Scaffold (TypeScript)
Generate TypeScript unit test skeletons (Jest/Vitest) from specifications.
typescript-standard
Apply opinionated TypeScript and testing standards — strict mode with no any, 10-20 line methods, and a test-first loop using data builders, Faker, and Given-When-Then. Use when writing, reviewing, or testing TypeScript, setting up Jest or Playwright, or checking TS code against a project's conventions.
quality-gates-node
Quality gates determinísticos para aplicações e serviços Node.js, JavaScript e TypeScript. Use quando o usuário pedir "quality gate Node.js", ESLint ou tsc em Node.js, testes, cobertura, complexidade, SAST, SCA, build ou baseline para Node.js.
ts-quality
A TypeScript quality-checking workflow that runs the TypeScript compiler, ESLint, Prettier, and tests. TypeScript is JavaScript with static type checking; ESLint checks code patterns, and Prettier checks formatting.