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 commands/andronics/claude-plugin-typescript-pro/ts-monorepogit clone --depth 1 https://github.com/andronics/claude-plugin-typescript-proWrote 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/commands/andronics/claude-plugin-typescript-pro/ts-monorepo)<a href="https://agentmods.dev/commands/andronics/claude-plugin-typescript-pro/ts-monorepo"><img src="https://agentmods.dev/badge/commands/andronics/claude-plugin-typescript-pro/ts-monorepo.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.00020 | $0.02269 |
| Opus 5 | $0.00010 | $0.01135 |
| Sonnet 5 | $0.00004 | $0.00454 |
| Haiku 4.5 | $0.00002 | $0.00227 |
Grade C, and why
ts-monorepo 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.
find packages -name "dist" -type d -exec rm -rf {} + How it starts
The opening of the file, as written. The whole thing — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage TypeScript monorepo operations:
-
Detect Monorepo Setup
Check for monorepo configuration:
- pnpm: pnpm-workspace.yaml
- npm: package.json workspaces
- Yarn: yarn workspaces in package.json
- Nx: nx.json
- Turborepo: turbo.json
- Lerna: lerna.json
-
Command Router
Based on $ARGUMENTS:
init- Initialize TypeScript monoreporeferences- Set up project referencesbuild- Build all packages in dependency ordertest- Run tests across workspaceclean- Clean all build artifactsdeps- Analyze dependencies between packagesadd- Add new package to monorepo- (no args) - Show monorepo status
Command: init
Initialize TypeScript monorepo from scratch:
1. Choose Package Manager
- Recommend pnpm for best TypeScript support
- Support npm workspaces, Yarn, or pnpm
2. Create Workspace Structure
monorepo/
├── packages/
│ ├── core/ # Shared utilities
│ ├── ui/ # UI components
│ └── app/ # Main application
├── package.json # Root package
├── pnpm-workspace.yaml # Workspace config
├── turbo.json # Build orchestration
└── tsconfig.base.json # Shared TS config
3. Configure Root Package
{
"name": "monorepo-root",
"private": true,
"workspaces": ["packages/*"],
"scripts": {
"build": "turbo run build",
"test": "turbo run test",
"type-check": "turbo run type-check",
"clean": "turbo run clean"
},
"devDependencies": {
"typescript": "^5.5.0",
"turbo": "^2.0.0"
}
}
4. Create Workspace Config
# pnpm-workspace.yaml
packages:
- 'packages/*'
5. Set Up Base TypeScript Config
// tsconfig.base.json
{
"compilerOptions": {
"target": "ES2020",
"module": "ESNext",
"lib": ["ES2020"],
"moduleResolution": "bundler",
"strict": true,
"esModuleInterop": true,
"skipLibCheck": true,
"composite": true,
"declaration": true,
"declarationMap": true,
"sourceMap": true,
"incremental": true
}
}
6. Configure Turborepo
// turbo.json
{
"$schema": "https://turbo.build/schema.json",
"pipeline": {
"build": {
"dependsOn": ["^build"],
"outputs": ["dist/**", ".next/**"]
},
"test": {
"dependsOn": ["build"]
},
"type-check": {
"dependsOn": ["^build"]
},
"clean": {
"cache": false
}
}
}
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 · 416 lines · 0 tokens per session scan C b65736bccfcb
ts-monorepo is a command published in the GitHub repository andronics/claude-plugin-typescript-pro (4 stars, last pushed 10mo ago), licensed MIT. It adds 20 tokens to every session and 2,269 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.
setup-code-intelligence
Check code-intelligence prerequisites (ripgrep + a language server) and print install hints.
type-crusade
Unleash parallel TypeScript Purist agents to purge every any, as cast, and type sin across the codebase. No type sin survives.
vite-react-setup
Setup project React SPA mới với Vite + TypeScript + Tailwind CSS v3 + Vitest. Dùng khi bắt đầu dự án frontend mới, cần scaffold đầy đủ config, brand KZTEK colors, và test setup sẵn sàng.
typescript
Apply TypeScript best practices and coding standards.
scaffold-react
Quickly scaffold a new React + TypeScript project with Claude Code configuration.