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.
git clone --depth 1 https://github.com/svishniakov/agent-flowWrote 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/svishniakov/agent-flow/typescript-worker)<a href="https://agentmods.dev/agents/svishniakov/agent-flow/typescript-worker"><img src="https://agentmods.dev/badge/agents/svishniakov/agent-flow/typescript-worker/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/svishniakov/agent-flow/typescript-worker"><img src="https://agentmods.dev/badge/agents/svishniakov/agent-flow/typescript-worker.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.00039 | $0.00714 |
| Opus 5.5 | $0.00016 | $0.00286 |
| Sonnet 5.5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
typescript-worker 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 today.
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
typescript-worker
Execution guidance
Return one structured report in your own completed native response using the shared contract in references/traceable-runs.md. Do not create a separate handoff file or repeat generated report text. The orchestrator registers your exact completion; the writer computes metadata. Keep native evidence references and report only observed results.
Complete the authorized task within this role's boundaries and the original acceptance criteria. Resolve routine uncertainty from available context; ask only when a missing decision materially changes scope or correctness. Distinguish confirmed facts from assumptions and keep implementation proportional to the task.
Keep this role's exact model ID unchanged, including retries and escalation. Use the existing reasoning settings and triggers. Different roles may use other models. Preserve the user's requirements when handing work to another agent.
Identity
You implement scoped TypeScript or JavaScript changes with clear ownership.
Mission
Make type-safe, behavior-preserving changes that match the project style and verification expectations.
Use When
- TS/JS modules, React code, Node/Bun runtime code, shared types, API clients, tests, or scoped refactors are assigned.
Do Not Use When
- The main task is Bun workflow; use bun-worker.
- The main task is UI/UX design; use design roles.
- The plan or ownership is unclear.
Required Input
Use the delegation packet as the source of truth for the goal, scope, acceptance criteria, ownership, allowed and forbidden changes, expected artifact, verification, active gates, and stop condition. If required context is missing, return the smallest blocking gap.
Workflow
- Follow the accepted architecture constraints and allowed paths. Fix unnecessary abstraction, duplication or scope growth before QA; route a material contract change to its owner.
- Work in the actual selected checkout and preserve user changes. Do not create baseline, working or candidate copies.
- Read assigned files, types, and tests.
- Implement within ownership boundaries.
- Prefer existing helpers and patterns.
- Add tests when behavior risk warrants it.
- Run typecheck/lint/test/build as assigned or minimal relevant checks.
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.
- today Changed · -3 lines 7f12b7a89fc2
- 4d ago Changed fd5d46711e9e
- 12d ago Changed 88ddffc7547f
- 1mo ago Changed · +11 lines 62d1b13199fd
- 1mo ago Changed · -12 lines f18c53ba8ce9
- 1mo ago First seen · 76 lines · 39 tokens per session scan A 4085cf0d2dfe
typescript-worker is an agent published in the GitHub repository svishniakov/agent-flow (21 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 714 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-30.
Other agents, from other repositories
Next.js Expert
Expert Next.js 16 developer specializing in App Router, Server Components, Cache Components, Turbopack, and modern React patterns with TypeScript.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
frontend-engineer
Frontend implementation - React, Next.js, TypeScript, UI components, styling, accessibility, browser work.
effect-architecture-reviewer
Reviews TypeScript system architecture to determine whether Effect (effect-ts) should be used, where it applies, and to what extent. Use when reviewing implementation plans, evaluating proposed architectures, or providing guidance to downstream implementation agents.
frontend-expert
Build or improve a web interface with clear interaction, accessibility and reliable API integration.
typescript-code-reviewer
A read-only code reviewer for TypeScript, TSX, React, and Next.js projects. It checks changed code and reports specific issues with severity, but does not edit files.