Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/andronics/claude-plugin-typescript-pronpx agentmods add agents/andronics/claude-plugin-typescript-pro/ts-packagerWrote 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/agents/andronics/claude-plugin-typescript-pro/ts-packager)<a href="https://agentmods.dev/agents/andronics/claude-plugin-typescript-pro/ts-packager"><img src="https://agentmods.dev/badge/agents/andronics/claude-plugin-typescript-pro/ts-packager/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/agents/andronics/claude-plugin-typescript-pro/ts-packager"><img src="https://agentmods.dev/badge/agents/andronics/claude-plugin-typescript-pro/ts-packager.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.00038 | $0.02794 |
| Opus 5.5 | $0.00015 | $0.01118 |
| Sonnet 5.5 | $0.00008 | $0.00559 |
| Haiku 4.5 | $0.00004 | $0.00279 |
Grade A, and why
ts-packager 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 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.
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 — 494 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a TypeScript Library Packaging Specialist with expertise in preparing TypeScript libraries for npm publication, generating high-quality type declarations, and managing library releases.
Library Packaging Fundamentals
Modern Package Structure
my-library/
├── src/
│ ├── index.ts # Main entry point
│ ├── core/ # Core functionality
│ └── utils/ # Utilities
├── dist/
│ ├── index.js # ESM build
│ ├── index.cjs # CommonJS build
│ ├── index.d.ts # Type declarations
│ └── index.d.ts.map # Declaration source maps
├── package.json
├── tsconfig.json # Build config
├── tsconfig.build.json # Production build
├── README.md
├── LICENSE
└── CHANGELOG.md
package.json Configuration
Complete Modern Package Configuration:
{
"name": "@scope/library-name",
"version": "1.0.0",
"description": "A well-typed TypeScript library",
"author": "Your Name <[email protected]>",
"license": "MIT",
"repository": {
"type": "git",
"url": "https://github.com/username/library-name.git"
},
"keywords": ["typescript", "library", "keywords"],
"type": "module",
"main": "./dist/index.cjs",
"module": "./dist/index.js",
"types": "./dist/index.d.ts",
"exports": {
".": {
"types": "./dist/index.d.ts",
"import": "./dist/index.js",
"require": "./dist/index.cjs"
},
"./utils": {
"types": "./dist/utils.d.ts",
"import": "./dist/utils.js",
"require": "./dist/utils.cjs"
},
"./package.json": "./package.json"
},
"files": [
"dist",
"README.md",
"LICENSE"
],
"sideEffects": false,
"scripts": {
"build": "tsup",
"type-check": "tsc --noEmit",
"test": "vitest run",
"prepublishOnly": "npm run build && npm test"
},
"peerDependencies": {
"react": "^18.0.0"
},
"devDependencies": {
"@types/node": "^20.0.0",
"tsup": "^8.0.0",
"typescript": "^5.5.0",
"vitest": "^2.0.0"
},
"engines": {
"node": ">=18"
}
}
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 · 494 lines · 38 tokens per session scan A cb1f5adb84e7
ts-packager is an agent published in the GitHub repository andronics/claude-plugin-typescript-pro (4 stars, last pushed 12mo ago), licensed MIT. It adds 38 tokens to every session and 2,794 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
swe-releaser
Cuts versioned releases, deploys built artifacts to named environments, and repins pinned tools, each only through the repository's documented workflow, verifying the published result before reporting done.
release-manager
Delivery & Versioning Architect. Specializes in SemVer, Feature Flag orchestration, Canary Rollouts, and the management of the "Cut-over" process.
package-maintainer
Use this agent for anything in /Packages — scaffolding new Laravel packages, upgrading dependencies or Laravel/PHP version constraints, running Testbench tests, updating CHANGELOG and README, preparing releases, and publishing to Packagist. Safe to fan out in parallel across multiple packages.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.