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 Cypsy1714/cchad --skill typescript-skillgit clone --depth 1 https://github.com/Cypsy1714/cchadWrote 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/cypsy1714/cchad/typescript-skill)<a href="https://agentmods.dev/skills/cypsy1714/cchad/typescript-skill"><img src="https://agentmods.dev/badge/skills/cypsy1714/cchad/typescript-skill/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/cypsy1714/cchad/typescript-skill"><img src="https://agentmods.dev/badge/skills/cypsy1714/cchad/typescript-skill.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.00020 | $0.00278 |
| Opus 5.5 | $0.00008 | $0.00111 |
| Sonnet 5.5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
typescript-conventions 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.
What it actually says
TypeScript conventions
Types
- Turn on
strictand keep it on. Fix type errors; don't paper over them. - Avoid
any. Reach forunknownat boundaries and narrow it, or write a proper type. Useascasts only when you truly know better than the compiler. - Model states with discriminated unions (
type Result = Ok | Err) instead of optional-field grab-bags. Let the compiler force you to handle every case. - Prefer
typealiases for unions and function types; useinterfacefor object shapes you expect to extend or implement.
Safety
- Don't abuse the non-null assertion
!. Handle theundefinedcase or narrow it. - Type function inputs and public return values explicitly; let inference handle local variables.
- Use
readonlyandas constfor data that shouldn't change.
Practical
- Derive types from a single source of truth (
typeof,keyof, indexed access, utility types) rather than hand-copying shapes. - Validate external data (API responses, env) at the boundary with a schema library so the rest of the code can trust its types.
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 · 28 lines · 20 tokens per session scan A 50fe13669ffd
typescript-conventions is a skill published in the GitHub repository Cypsy1714/cchad (1 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 278 once invoked, about $0.0001 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
typescript-coder
Implements TypeScript/JavaScript code following established architecture and coding guidelines. Use when implementing features designed by typescript-architect.
typescript-testing
TypeScript testing patterns with Jest/Vitest including unit tests, integration tests, mocking strategies, and coverage. Use when writing TypeScript tests.
typescript-architect
Creates high-level TypeScript architecture with interfaces, test stubs, and module structure. Use when designing TypeScript/JavaScript projects or features.
senior-frontend
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
clean-code-ts
Use when writing or reviewing TypeScript — deeper idioms (eliminate any, discriminated unions, narrowing, exhaustiveness, schema-derived types, async correctness).
node-backend
Node.js backend development patterns for Express, NestJS, Fastify, and Hono. Use when implementing APIs, authentication, middleware, services, and server-side logic with Node.js and TypeScript. Provides project structure, code patterns, and best practices.