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 Benknightdark/neo-skills --skill neo-typescriptgit clone --depth 1 https://github.com/Benknightdark/neo-skillsWrote 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/benknightdark/neo-skills/neo-typescript)<a href="https://agentmods.dev/skills/benknightdark/neo-skills/neo-typescript"><img src="https://agentmods.dev/badge/skills/benknightdark/neo-skills/neo-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/benknightdark/neo-skills/neo-typescript"><img src="https://agentmods.dev/badge/skills/benknightdark/neo-skills/neo-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.00063 | $0.00727 |
| Opus 5 | $0.00032 | $0.00364 |
| Sonnet 5 | $0.00013 | $0.00145 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
neo-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 11d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neo TypeScript Expert Skill
This skill guides the AI Agent to write code that adheres to the strictest type safety, high maintainability, and advanced meta-programming flexibility, while thoroughly preventing runtime issues such as ESM/CJS interoperability pitfalls.
💡 Gotchas
- Aliasing Writable Reference Bypasses Readonly: In TypeScript,
readonlyonly restricts the assignment to the property itself. The internal members of the referenced object/array remain mutable. Furthermore, a readonly object can be assigned to a writable alias, which completely bypasses compiler readonly checks. - Fatal Crash via Partial esModuleInterop: Enabling
allowSyntheticDefaultImportswithoutesModuleInteropallows code to pass compile-time type checks but causes an immediate runtime crash (TypeError: default is not a function) due to the lack of__importDefaultemit helpers in transpile output. - Double Default Trap for Library Creators: Using
export defaultin libraries forces Node.js ESM consumers to call.default()to access the module. The golden standard is to completely abandonexport defaultand adoptexport =or named exports instead.
📋 Static Code & Type Safety Review SOP
When asked to write, modify, refactor, or review TypeScript code, strictly execute the following workflow:
Step 1 — Project Environment Perception (Perceive)
- Inspect the project's
tsconfig.jsonsettings, focusing specifically on the configuration of"strict": true,"strictNullChecks", and"strictFunctionTypes". - Identify the target module format and resolution mechanism (
"moduleResolution").
Step 2 — Core Type Routing (Reason)
Based on the specific technical domain of the task, progressively disclose and load the corresponding reference files in the skill. Do not load all files at once to save context token space:
- Basics, Narrowing, Classes, & Function Design ➡️ Load type-system-basics.md
- Generic Constraints, Variance, & Advanced Types from Types ➡️ Load advanced-meta-types.md
- Structural Compatibility, Decorators, & ESM/CJS Interop ➡️ Load compatibility-and-interop.md
What ships with it
5 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.
- 11d ago First seen · 47 lines · 63 tokens per session scan A a049f2a0217b
neo-typescript is a skill published in the GitHub repository Benknightdark/neo-skills (7 stars, last pushed 5d ago), licensed MIT. It adds 63 tokens to every session and 727 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
adk
Use this skill when you've got questions about the Botpress Agent Development Kit (ADK) - like when you're building a feature that involves tables, actions, tools, workflows, conversations, files, knowledge bases, triggers, or Zai.
solana-kit
Complete guide for @solana/kit - the modern, tree-shakeable, zero-dependency JavaScript SDK from Anza. Covers RPC connections, signers, transaction building with pipe, signing, sending, and account fetching with full TypeScript support.
solana-kit-migration
Helps developers understand when to use @solana/kit vs @solana/web3.js (v1), provides migration guidance, API mappings, and handles edge cases for Solana JavaScript SDK transitions.
typescript
Use when writing or hardening TypeScript in strict mode. Covers advanced types, discriminated unions, runtime validation at trust boundaries, generics, and removing any from an existing codebase.
coding-standards
React 19 and TypeScript coding standards for Portfolio Buddy 2. Use when: writing new components, reviewing code, refactoring, or ensuring consistency. Contains component patterns, TypeScript rules, and best practices.
portfolio-context
Auto-loaded context for Portfolio Buddy 2 development. Use for ANY task involving: React 19 development, TypeScript, portfolio analysis features, metrics calculations, trading strategy comparison, or working with the Portfolio Buddy 2 codebase. Contains tech stack, known issues, and architectural constraints.