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/andr-ca/agentharness/typescript-conventionsnpx skills add andr-ca/agentharness --skill typescript-conventionsgit clone --depth 1 https://github.com/andr-ca/agentharnessWhat 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.00043 | $0.00886 |
| Opus 5 | $0.00022 | $0.00443 |
| Sonnet 5 | $0.00009 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00089 |
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 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Conventions
This file is self-contained for day-to-day use. Deeper reference (needs
the full harness checkout): languages/typescript/CONVENTIONS.md (full
examples including generics and import grouping) and
frameworks/react/CONVENTIONS.md (React/JSX-specific additions).
Naming
camelCase— functions, variables, method names.PascalCase— classes, interfaces, type aliases, enum names.UPPER_SNAKE_CASE— module-level constants.- Enum members:
PascalCase. - Generic type params:
T/Ufor simple one-liners; descriptive names (TEntity,TResponse) for complex or nested generics.
Imports & module structure
Group: external packages → internal modules → type-only imports.
Separate each group with a blank line. Prefer import type for
type-only imports (helps tools that strip types without full parsing).
import fs from 'fs';
import express from 'express';
import { UserRepository } from './repositories/UserRepository';
import type { User } from './types';
Private members: # over _prefix
Prefer native # private fields (ES2022+/TS 3.8+) in new code — real
runtime privacy, not a convention that's still readable via ["_name"].
Don't rewrite working _prefix code on sight; it's not deprecated.
class TokenStore {
#tokens: Map<string, string> = new Map(); // true runtime privacy
#rotate(): void { /* ... */ }
}
Null vs. Undefined
Pick based on what absence means, then apply it consistently:
undefined(via?) — "not provided / not yet set."null— an explicit "no value" the code sets deliberately (nullable column, "user cleared this field").- Do not mix both for the same kind of absence in one module.
Pitfalls to catch in review
// WRONG: async function catches error, logs it, then resolves — hides failure
async function save(data: Data): Promise<void> {
try {
await db.write(data);
} catch (err) {
logger.error('save failed', err);
// caller sees a successful promise despite the failure
}
}
// RIGHT: rethrow after logging so the caller can handle the failure
async function save(data: Data): Promise<void> {
try {
await db.write(data);
} catch (err) {
logger.error('save failed', err);
throw err; // caller knows this failed
}
}
// Type-cast escape hatch silences the compiler, not the bug
const result = someValue as SomeType; // risky without a runtime check
// Prefer a type guard:
function isSomeType(v: unknown): v is SomeType { /* ... */ }
// Non-null assertion hides null/undefined bugs
const name = user!.profile!.name; // crashes at runtime if null
// RIGHT: optional chaining + fallback
const name = user?.profile?.name ?? 'Unknown';
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 · 110 lines · 43 tokens per session scan A c042e576389f
typescript-conventions is a skill published in the GitHub repository andr-ca/agentharness (1 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 886 once invoked, about $0.0002 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
architecture-audit
Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…
bun-toolkit
JS/TS/JSX toolkit with Bun awareness. Use when using Bun as a runtime, test runner, or package manager in JavaScript and TypeScript projects.
ban-type-assertions
Enforce a TypeScript policy that bans as type assertions and replace casts with compiler-verified narrowing or runtime validation. Use when introducing the ESLint rule, removing violations, reviewing assertion workarounds, or designing typed data boundaries.
typescript
Write, review, and refactor TypeScript for readability, type safety, and runtime correctness (Node.js/React/shared libs). Use when creating TS modules, modeling domain types, handling errors (Result/Either), validating external inputs (Zod/io-ts), organizing imports, or preventing cyclic dependencies. NOT for choosing…
setup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.