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 b33eep/claude-code-setup --skill standards-typescriptgit clone --depth 1 https://github.com/b33eep/claude-code-setupWrote 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/b33eep/claude-code-setup/standards-typescript)<a href="https://agentmods.dev/skills/b33eep/claude-code-setup/standards-typescript"><img src="https://agentmods.dev/badge/skills/b33eep/claude-code-setup/standards-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/b33eep/claude-code-setup/standards-typescript"><img src="https://agentmods.dev/badge/skills/b33eep/claude-code-setup/standards-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.00033 | $0.02597 |
| Opus 5.5 | $0.00013 | $0.01039 |
| Sonnet 5.5 | $0.00007 | $0.00519 |
| Haiku 4.5 | $0.00003 | $0.00260 |
Grade A, and why
standards-typescript scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(url); How it starts
The opening of the file, as written. The whole thing — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Coding Standards
Core Principles
- Simplicity: Simple, understandable code
- Readability: Readability over cleverness
- Maintainability: Code that's easy to maintain
- Testability: Code that's easy to test
- DRY: Don't Repeat Yourself - but don't overdo it
General Rules
- Early Returns: Use early returns to avoid nesting
- Descriptive Names: Meaningful names for variables and functions
- Minimal Changes: Only change relevant code parts
- No Over-Engineering: No unnecessary complexity
- Minimal Comments: Code should be self-explanatory. No redundant comments!
Naming Conventions
| Element | Convention | Example |
|---|---|---|
| Variables/Functions | camelCase | getUserById, isActive |
| Classes/Interfaces/Types | PascalCase | UserService, ApiClient |
| Constants | UPPER_SNAKE_CASE | MAX_RETRY_COUNT |
| Private | Prefix with _ or # |
_internalMethod, #privateField |
| Files | kebab-case or camelCase | user-service.ts, userService.ts |
| Interfaces | No I prefix |
User not IUser |
| Type aliases | PascalCase | UserId, HttpMethod |
| Event Handlers | Prefix with handle |
handleClick, handleSubmit |
Project Structure
myproject/
├── src/
│ ├── index.ts # Entry point
│ ├── config.ts # Settings, env vars
│ ├── types/
│ │ └── index.ts # Shared types
│ ├── models/
│ │ └── user.ts # Domain models
│ ├── services/
│ │ └── user-service.ts # Business logic
│ ├── repositories/
│ │ └── user-repo.ts # Data access
│ └── utils/
│ └── helpers.ts # Utility functions
├── tests/
│ ├── services/
│ │ └── user-service.test.ts
│ └── setup.ts
├── package.json
├── tsconfig.json
└── README.md
Code Style
// Use explicit types for function parameters and return values
function getUserById(userId: string): User | undefined {
if (!userId) {
throw new Error("userId cannot be empty");
}
// implementation...
}
// Prefer interfaces for object shapes
interface User {
id: string;
name: string;
email: string;
age?: number;
}
// Use type aliases for unions, intersections, or primitives
type UserId = string;
type HttpMethod = "GET" | "POST" | "PUT" | "DELETE";
type Result<T> = { success: true; data: T } | { success: false; error: string };
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.
- 1mo ago First seen · 359 lines · 33 tokens per session scan A 330c7d927835
standards-typescript is a skill published in the GitHub repository b33eep/claude-code-setup (57 stars, last pushed 14d ago), licensed MIT. It adds 33 tokens to every session and 2,597 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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).
typescript-conventions
Idiomatic, type-safe TypeScript. Use when writing or reviewing TypeScript.