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 skills add alexei-led/architect --skill tools-typescriptgit clone --depth 1 https://github.com/alexei-led/architectWrote 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/alexei-led/architect/tools-typescript)<a href="https://agentmods.dev/skills/alexei-led/architect/tools-typescript"><img src="https://agentmods.dev/badge/skills/alexei-led/architect/tools-typescript/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/skills/alexei-led/architect/tools-typescript"><img src="https://agentmods.dev/badge/skills/alexei-led/architect/tools-typescript.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.00108 | $0.01433 |
| Opus 5.5 | $0.00043 | $0.00573 |
| Sonnet 5.5 | $0.00022 | $0.00287 |
| Haiku 4.5 | $0.00011 | $0.00143 |
Grade A, and why
tools-typescript 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript / JavaScript tools
Dependency and quality evidence for TS/JS targets. These tools give the module graph, cycles, unused surface, and type/lint state — the inputs to dependency, structural, and fitness scoring.
Evidence dimensions: dependency, structural, semantic (tsc).
When to use
Use when the system map shows a package.json / tsconfig.json. Pick the tool
to the question: graph and cycles (dependency-cruiser, madge), workspace/package
boundaries, dead/unused exports and deps (knip), type correctness (tsc), boundary
lint rules (ESLint). Use the results to judge module boundaries, dependency
direction, coupling, and architecture fitness.
Commands
Resolve the package root and runner without changing dependency state:
- Read
package.jsonforpackageManager,scripts, andworkspaces. - Check workspace manifests and current lockfiles:
pnpm-workspace.yaml,pnpm-lock.yaml,yarn.lock,package-lock.json,bun.lock, andbun.lockb. - If those signals conflict, record the runner as ambiguous and use only an explicit configured script or ask which package root owns the check.
- Prefer a configured script after inspecting it for install or download
commands. Otherwise run only a proven executable already in that package
root's
node_modules/.bin.
Do not install or download analysis tools during a review. npm exec, npx,
bunx, pnpm dlx, and yarn dlx can acquire missing packages; do not use them
as an installation fallback. Redirect caches to $TMPDIR.
# Package-manager, workspace, and script discovery
node -e 'const p=require("./package.json"); console.log(JSON.stringify({packageManager:p.packageManager??null,workspaces:p.workspaces??null,scripts:p.scripts??{}},null,2))'
ls package-lock.json yarn.lock pnpm-lock.yaml pnpm-workspace.yaml bun.lock bun.lockb 2>/dev/null
# Use an inspected configured script with the detected package manager
# pnpm: pnpm run; npm: npm run; Yarn: yarn run; Bun: bun run
<detected-runner> run <configured-script>
# Otherwise prove each local binary exists, then run it directly
test -x node_modules/.bin/depcruise && node_modules/.bin/depcruise src --include-only "^src" --config .dependency-cruiser.cjs
test -x node_modules/.bin/madge && node_modules/.bin/madge --circular --extensions ts,tsx src
test -x node_modules/.bin/knip && node_modules/.bin/knip
test -x node_modules/.bin/tsc && node_modules/.bin/tsc --noEmit
test -x node_modules/.bin/eslint && ESLINT_CACHE_LOCATION=$TMPDIR/eslint-cache node_modules/.bin/eslint . --max-warnings 0
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 · 124 lines · 108 tokens per session scan A 3c010eb5ca07
tools-typescript is a skill published in the GitHub repository alexei-led/architect (3 stars, last pushed 3mo ago), licensed MIT. It adds 108 tokens to every session and 1,433 once invoked, about $0.0004 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 skills, from other repositories
neo4j-driver-javascript-skill
Neo4j JavaScript/TypeScript Driver v6 — driver lifecycle, executeQuery, managed transactions (executeRead/executeWrite), session.run, Integer handling, JSON serialization, record access, async/await patterns, TypeScript types, error handling, and connection setup for Node.js and browser. Use when writing JS/TS code…
sveltekit-and-svelte5-runes
Complete architecture patterns, state management with Svelte 5 Runes ($state, $derived, $effect, $props), SvelteKit SSR/streaming pipelines, form actions, and production anti-patterns.
electron-crossplatform-performance
Production architecture, multi-process IPC security, V8 memory management, native node modules, window lifecycle optimization, and cross-platform desktop execution using Electron. Use when building, hardening, or tuning performance for enterprise Electron apps across Windows, macOS, and Linux.
prisma-orm-patterns-and-migrations
Best practices for Prisma ORM schema design, high-performance query optimization, preventing N+1 problems, zero-downtime database migrations, connection pooling, and multi-tenant data modeling. Use when building Node.js/TypeScript applications with Prisma.
typescript-react-nextjs-patterns
Production-grade TypeScript reference for React & Next.js frontend development. Covers type narrowing, component Props, generic hooks, discriminated unions, as const, satisfies, Zod validation, TanStack Query, server/client boundaries, forms, state management, performance, accessibility, debugging, and code review.…
drizzle-orm-expert
Expert in Drizzle ORM for TypeScript — schema design, relational queries, migrations, serverless DB integration. Use when building type-safe database layers with Drizzle, migrating from Prisma, or optimizing edge runtime DB access.