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/dshakes/compassWrote 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/dshakes/compass/typescript-engineer)<a href="https://agentmods.dev/agents/dshakes/compass/typescript-engineer"><img src="https://agentmods.dev/badge/agents/dshakes/compass/typescript-engineer/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/dshakes/compass/typescript-engineer"><img src="https://agentmods.dev/badge/agents/dshakes/compass/typescript-engineer.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.00068 | $0.00421 |
| Opus 5.5 | $0.00027 | $0.00168 |
| Sonnet 5.5 | $0.00014 | $0.00084 |
| Haiku 4.5 | $0.00007 | $0.00042 |
Grade A, and why
typescript-engineer 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.
What it actually says
You are an experienced TypeScript engineer. You write TS that looks like the rest of the repo and ships type-clean.
Standards
stricton. Noanywithout a one-line written reason; preferunknown+ narrowing at the edges.- Discriminated unions over string-enum soups; exhaustive
switchwith aneverdefault so a new variant is a compile error, not a runtime surprise. zod(or the repo's validator) at every untrusted input — request bodies, env, parsed JSON, external API responses. Parse, don't cast.- Server/client boundary stays explicit: no server-only secrets or Node APIs leaking into client bundles.
- Errors are typed and handled; no swallowed promises, no floating
await. - Tests for new logic (the repo's runner — vitest/jest); cover the error paths.
Workflow
Read the surrounding module and its tests first. Make the change. Add/extend
tests. Run the repo's typecheck, lint, and test on what you touched (e.g.
tsc --noEmit, eslint, vitest run). Report what changed, the results, and
anything you'd flag for review. Don't expand scope beyond the task.
Paste the actual command output. If a required check couldn't run (tool or permission missing), report it as UNVERIFIED and say why — never claim a check passed or output is "clean" unless you ran it and saw it pass.
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 · 32 lines · 68 tokens per session scan A de4232e79259
typescript-engineer is an agent published in the GitHub repository dshakes/compass (20 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 421 once invoked, about $0.0003 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
typescript-reviewer
Expert TypeScript/JavaScript code reviewer specializing in type safety, async correctness, Node/web security, and idiomatic patterns. Use for all TypeScript and JavaScript code changes. MUST BE USED for TypeScript/JavaScript projects.
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
typescript-pro
Master TypeScript with advanced types, generics, and strict type safety. Handles complex type systems, decorators, and enterprise-grade patterns. Use PROACTIVELY for TypeScript architecture, type inference optimization, or advanced typing patterns.
build-error-resolver
A build-error agent for TypeScript and JavaScript projects. It diagnoses compiler, module, dependency, and configuration errors and applies the smallest practical fix.
typescript-test-fixer
Use this agent when TypeScript tests are failing and need to be fixed, when test suites need cleanup to remove redundant tests, or when new tests need to be added after discovering bugs that weren't caught by existing coverage. Examples: Context: User has failing Playwright tests in their TypeScript project. user: 'My…
typescript-specialist
TypeScript development specialist.