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-initgit clone --depth 1 https://github.com/andronics/claude-plugin-typescript-proWhat 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.00014 | $0.00419 |
| Opus 5 | $0.00007 | $0.00210 |
| Sonnet 5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
ts-init 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.
What it actually says
Initialize a new TypeScript project with optimal configuration. Detect the project type and framework, then set up:
-
Detect Project Context
- Check for existing package.json and framework indicators
- Identify: React, Vue, Svelte, Node, Express, NestJS, or generic TS project
- Detect build tool: Vite, webpack, esbuild, or none
-
Initialize TypeScript
- Install TypeScript and @types packages appropriate for the framework
- Create tsconfig.json optimized for the detected project type
- Set up strict mode with appropriate compiler options
- Configure module resolution and path mapping
-
Set Up Tooling
- Install and configure ESLint with typescript-eslint
- Set up Prettier with TypeScript support
- Create .editorconfig for consistency
- Add pre-commit hooks with husky + lint-staged
-
Create Project Structure
- Set up src/ directory with index.ts
- Create appropriate test setup (Vitest, Jest, or Playwright)
- Add .gitignore for TypeScript artifacts
- Create basic README with setup instructions
-
Configure Scripts
- Add npm scripts for build, dev, test, type-check, lint
- Set up watch mode for development
- Configure CI-ready scripts
-
Framework-Specific Setup
- React: tsconfig with JSX, React types, testing-library
- Vue: vue-tsc, Volar configuration
- Node/Express: Node types, nodemon, ES modules config
- Library: Declaration files, dual package setup
Argument: $ARGUMENTS (optional: "react", "vue", "node", "library", or auto-detect)
After setup, provide a summary of what was configured and next steps.
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 · 45 lines · 14 tokens per session scan A f10c9cb7b215
ts-init is a command published in the GitHub repository andronics/claude-plugin-typescript-pro (4 stars, last pushed 10mo ago), licensed MIT. It adds 14 tokens to every session and 419 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.