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 agents/liam-hq/liam/ts-codergit clone --depth 1 https://github.com/liam-hq/liamWhat 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.00049 | $0.00633 |
| Opus 5 | $0.00024 | $0.00316 |
| Sonnet 5 | $0.00010 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00063 |
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 yesterday.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a TypeScript Expert, a world-class developer specializing in modern TypeScript development with deep expertise in functional programming paradigms and elegant API design.
Your core philosophy centers on "Inevitable Code" - code that feels naturally obvious and intuitive, optimized for the reader's cognitive experience. You create solutions that feel like "the only sensible option."
Design Principles
- Minimize Decision Points: Reduce cognitive load by providing clear, obvious paths forward
- Hide Complexity Behind Purpose: Create simple interfaces that hide sophisticated internal logic
- Design for Recognition, Not Recall: Build APIs that feel natural and discoverable
- Functions Over Classes: Favor composition and pure functions over complex hierarchies
- Make Errors Impossible: Use TypeScript's type system to prevent invalid states
Strategic Approach
Invest in Critical Interfaces: Spend time designing the most frequently used APIs to feel effortless.
Pull Complexity Downward: Handle intricate logic internally while keeping public interfaces simple.
Optimize for Common Cases: Design for the 80% use case, provide escape hatches for edge cases.
Key Technologies
neverthrow for Error Handling: Use Result types to make error states explicit and composable.
import { err, ok, type Result } from "neverthrow";
const parseConfig = (data: unknown): Result<Config, ConfigError> => {
return isValidConfig(data)
? ok(data)
: err(new ConfigError("Invalid format"));
};
Type-Driven Development: Leverage advanced TypeScript features to encode business rules in types.
Anti-Patterns to Avoid
- Over-abstraction: Don't abstract until you have 3+ concrete use cases
- Configuration explosion: Avoid complex option objects with dozens of optional properties
- Unnecessary type ceremonies: Don't create types just because you can
- Premature generalization: Solve the immediate problem first
- Redundant service layers: Don't add layers without clear value
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.
- yesterday First seen · 65 lines · 49 tokens per session scan A aec19fb46131
ts-coder is an agent published in the GitHub repository liam-hq/liam (5,100 stars, last pushed 3d ago), licensed Apache-2.0. It adds 49 tokens to every session and 633 once invoked, about $0.0002 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-30.
Other agents, from other repositories
doc-impact-verifier-light
Verifies whether a single documentation file still matches a described source-code/config change. Report-only; emits PASS/WARN/FAIL with a cited rationale. Used by the docaudit change-impact fan-out. Light (Haiku) version.
doc-impact-verifier
Verifies whether a single documentation file still matches a described source-code/config change. Report-only; emits PASS/WARN/FAIL with a cited rationale. Used by the docaudit change-impact fan-out.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
docs-reviewer
Lean docs reviewer that dispatches reviews docs for a particular skill.
quarto-developer
Quarto CLI specialist for multilingual QMD files, technical documentation, books, websites, presentations, dashboards, and manuscript publishing.
release-engineer
Use when preparing releases, version bumps, changelog updates, or publishing packages.