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/sapientsai/microsoft-mcp-server/typescript-standardsnpx skills add sapientsai/microsoft-mcp-server --skill typescript-standardsgit clone --depth 1 https://github.com/sapientsai/microsoft-mcp-serverWrote 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/sapientsai/microsoft-mcp-server/typescript-standards)<a href="https://agentmods.dev/skills/sapientsai/microsoft-mcp-server/typescript-standards"><img src="https://agentmods.dev/badge/skills/sapientsai/microsoft-mcp-server/typescript-standards.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.1 | $0.00062 | $0.02434 |
| Opus 5 | $0.00031 | $0.01217 |
| Sonnet 5 | $0.00012 | $0.00487 |
| Haiku 4.5 | $0.00006 | $0.00243 |
Grade C, and why
typescript-standards scanned grade C 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .git This is a copy
100% identical to typescript-standards — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Project Standards
Overview
This skill helps you create professional TypeScript libraries using the typescript-library-template pattern and apply these standards to existing projects. It provides a modern, production-ready setup with dual module format support, comprehensive testing, and consistent code quality tooling.
When to Use This Skill
Trigger this skill when:
- Creating a new TypeScript library or npm package
- Standardizing build scripts across TypeScript projects
- Setting up or migrating to dual module format (CommonJS + ES modules)
- Configuring modern tooling (tsup, Vitest, ESLint, Prettier)
- Applying consistent code quality standards
- Publishing packages to npm
- Migrating from older build tools (webpack, rollup, tsc alone)
Quick Start
Scenario 1: Creating a New Project
# Clone the template
git clone https://github.com/jordanburke/typescript-library-template.git my-library
cd my-library
# Remove template's git history
rm -rf .git
git init
# Install dependencies
pnpm install
# Customize (see references/template-setup.md for checklist)
# - Update package.json (name, description, repository)
# - Update README.md
# - Add your code to src/
# Validate everything works
pnpm validate
Scenario 2: Applying Standards to Existing Project
See references/standardization.md for detailed migration guide. Quick version:
- Update scripts in package.json to standardized pattern
- Install tooling: tsup, vitest, eslint, prettier
- Copy configs: tsup.config.ts, vitest.config.ts, eslint.config.mjs
- Update build outputs: Dual module format with proper exports
- Run validation:
pnpm validate
Core Standards
Script Commands
The template follows a consistent command pattern:
Main validation command:
pnpm validate # Format → Lint → Test → Build (use before commits)
Individual operations:
# Formatting
pnpm format # Write formatted code
pnpm format:check # Validate formatting only
# Linting
pnpm lint # Fix ESLint issues
pnpm lint:check # Check ESLint issues only
# Testing
pnpm test # Run tests once
pnpm test:watch # Watch mode
pnpm test:coverage # With coverage report
pnpm test:ui # Interactive UI
# Building
pnpm build # Production build (dist/)
pnpm dev # Development watch (lib/)
pnpm ts-types # Type check only
What ships with it
4 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.
- 5d ago First seen · 372 lines · 62 tokens per session scan C f2235c713060
typescript-standards is a skill published in the GitHub repository sapientsai/microsoft-mcp-server (1 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 2,434 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to typescript-standards, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.
aws-sst-development
SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework. Use when writing or editing sst.config.ts, building infra/ modules (sst.aws.Function/Bucket/Dynamo/Cron/Service/Router, sst.Secret, sst.Linkable, raw aws. Pulumi resources), wiring resource links,...
league-akari-shard-development
Use when creating, extending, refactoring, splitting, or reviewing League Akari main or renderer shards, including shard file organization, controller/loader/executor/handler boundaries, naming conventions, renderer TSX usage, platform guards, and public contract compatibility.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
migrate-better-result-3
Migrate a TypeScript codebase from better-result 2.x to 3.0. Use when upgrading better-result across the TaggedError syntax, removed Result serialization helpers, recovery inference, matching, or retry APIs.