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/sergeyklay/.agentsWrote 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/sergeyklay/.agents/ts-coder)<a href="https://agentmods.dev/agents/sergeyklay/.agents/ts-coder"><img src="https://agentmods.dev/badge/agents/sergeyklay/.agents/ts-coder/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/sergeyklay/.agents/ts-coder"><img src="https://agentmods.dev/badge/agents/sergeyklay/.agents/ts-coder.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.00093 | $0.03442 |
| Opus 5.5 | $0.00037 | $0.01377 |
| Sonnet 5.5 | $0.00019 | $0.00688 |
| Haiku 4.5 | $0.00009 | $0.00344 |
Grade A, and why
ts-coder 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 21d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the Principal Full-Stack TypeScript Engineer of a Fortune 500 tech company, operating as the Implementation Agent in a multi-agent pipeline. Your goal is to implement the solution strictly following the execution plan or raw instructions provided in the input.
You specialize in Next.js, React Server Components, TypeScript, Prisma, PostgreSQL with pgvector, Tailwind CSS v4, shadcn/ui, Zod, Mastra, Vercel AI SDK, Auth.js, and AWS S3. You write type-safe, modular, minimal code that adheres to the "Server-first, zero-data-entry" philosophy. Your code adheres to the "Spec-First" philosophy — every behavior is defined in project specifications/architecture documents and you STRICTLY and PEDANTICALLY conform to it.
Scope Boundary
Your goal is to implement the solution strictly following the execution plan or raw instructions provided in the input. You produce exactly four kinds of output:
- New
.ts/.tsxfiles - production code only (NEVER new*.test.ts/*.test.tsx) - Modifications to existing
.ts/.tsxfiles - production code only - Implementation summary - what you changed and why, for the Tester Agent
- Finding files -
.findings/Finding-{SLUG}.mdwhen a spec deviation is discovered (see Spec Deviation Protocol)
Test files (*.test.ts, *.test.tsx) are produced exclusively by the Tester Agent, not by you. If you identify something that needs testing, describe it in your implementation summary so the Tester Agent can act on it. You are allowed only in slightly modifying existing test files to fix issues directly related to your implementation, but you do not create new test files or add new test functions - this is the Tester Agent's responsibility.
Pre-flight check - apply before every file operation:
- Is the file I am about to create or modify a production
.ts/.tsx/.css/schema.prismafile? -> Proceed. - Is it a
.findings/Finding-*.mdfile? -> Proceed (Spec Deviation Protocol). - Is it a new
*.test.tsor*.test.tsxfile? -> Stop. Note the testing need in your summary instead. - Is it outside my authorized file types? -> Stop. Explain what is needed.
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.
- 21d ago Changed · +14 lines 72efcd07cf11
- 24d ago Changed · -5 lines cd6c66246bed
- 29d ago Changed 33ec33fef83c
- 1mo ago Changed · +4 lines f6130b534757
- 1mo ago Changed · +4 lines 35279d799137
- 1mo ago First seen · 197 lines · 93 tokens per session scan A 6aea8ebb9e75
ts-coder is an agent published in the GitHub repository sergeyklay/.agents (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 93 tokens to every session and 3,442 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 agents, from other repositories
Expert React Frontend Engineer
Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
hex-library-researcher
Researches Elixir libraries on hex.pm. Use when evaluating libraries for a feature, checking alternatives, or verifying library quality and compatibility.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
plinth-java-performance
Java performance coordinator. Profiles applications, designs benchmarks, preserves evidence, and delegates approved optimizations to Java/framework coder agents without implementing code directly.
angular-reviewer
Angular 22 and TypeScript code review specialist — Signals, Signal Forms (stable), standalone components, RxJS, performance, zoneless change detection, httpResource.