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/sergeyzwezdin/huba/typescript-developernpx skills add sergeyzwezdin/huba --skill typescript-developergit clone --depth 1 https://github.com/sergeyzwezdin/hubaWrote 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/sergeyzwezdin/huba/typescript-developer)<a href="https://agentmods.dev/skills/sergeyzwezdin/huba/typescript-developer"><img src="https://agentmods.dev/badge/skills/sergeyzwezdin/huba/typescript-developer.svg" alt="Measured on agentmods" 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 | $0.00153 | $0.00750 |
| Opus 5 | $0.00077 | $0.00375 |
| Sonnet 5 | $0.00031 | $0.00150 |
| Haiku 4.5 | $0.00015 | $0.00075 |
Grade A, and why
typescript-developer 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 3d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Developer
Write clean, maintainable, type-safe TypeScript code following SOLID principles.
Core Principles
- Readable & maintainable: Write straightforward, clean code that's easy to understand and modify
- SOLID principles: Follow Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion
- Strong typing: Explicit types for all variables, parameters, and return values. Never use
any - Performance optimization: Use
Promise.all()and other standard techniques for large datasets - Zod-first validation: Define schemas first, infer types using
z.infer<typeof schema> - Documentation: Use JSDoc to document all public classes, functions, and methods
- Named exports only: No default exports. Explicit imports improve discoverability
- Arrow functions: Use arrow functions with explicit return types for all functions
- Single responsibility: Functions <20 LOC, focused purpose, early returns
- Prefer
undefined: Returnundefinedfor empty responses instead ofnull
Naming Conventions
- Files/directories: kebab-case (
user-service.ts,get-user.ts) - Classes: PascalCase (
UserService,TaskManager) - Types/Interfaces: PascalCase (
User,UserCardProps) - Functions/variables: camelCase (
getUser,userId) - Booleans: verb prefix (
isLoading,hasError,canDelete) - Constants: UPPERCASE for env (
API_URL), camelCase for objects - Hooks:
useprefix (useUser,useAuth) - Functions: start with verb (
get*,create*,format*,validate*)
Reference Documentation
Read the relevant reference when working on specific tasks:
- Types & interfaces: types.md — type-only imports, props types, RO-RO parameter pattern
- Function patterns: functions.md — arrow functions, async patterns, React hooks with stable refs
- Imports & exports: imports-exports.md — barrel exports, absolute paths, import organization
- Validation & Zod: validation.md — schema-first definitions, safe parsing, enum schemas, deprecated methods
- Error handling: error-handling.md — throw vs
undefined, type guard filtering, context checks - JSDoc: jsdoc.md — documentation standards, TypeDoc tags, coverage requirements
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.
- 3d ago First seen · 52 lines · 153 tokens per session scan A dd319e5b8515
typescript-developer is a skill published in the GitHub repository sergeyzwezdin/huba (10 stars, last pushed 5mo ago), licensed MIT. It adds 153 tokens to every session and 750 once invoked, about $0.0008 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
hns-moaiadk-patterns
Skill "hns-moaiadk-patterns" from modu-ai/moai-adk, covering moai-adk-go domain patterns, architecture quick reference, key source paths, pipeline specialist delegation map and template-first build cycle.
hns-oss-docs-i18n-rules
HARD i18n rules digest for the oss-docs harness specialists working on moai-adk-go README 4-locale set and the docs-site (adk.mo.ai.kr). Covers the canonical-locale chains, the 4-locale same-PR obligation, Mermaid TD-only, the no-emoji + icon-shortcode rule, emphasis-marker spacing, the URL blacklist, version SSOT…
frontend-typescript-rules
Applies React/TypeScript type safety, component design, and state management rules. Use when implementing React components.
typescript-rules
Applies type safety and error handling rules. Enforces no-any policy and type guards. Use when implementing TypeScript or reviewing types.
typescript-testing
Applies repository-aware TypeScript test design, behavior evidence, isolation, and mock-boundary criteria. Use when writing or reviewing unit tests.
python-run
Run and debug Python scripts in the project. Use when the user says "run python", "execute this script", "debug this py file", or wants to run/modify a .py file. Handles dependency checks, linting, execution, and error analysis.