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/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/dx-engineer)<a href="https://agentmods.dev/agents/infraspecdev/tesseract/dx-engineer"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/dx-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/infraspecdev/tesseract/dx-engineer"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/dx-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.00032 | $0.01214 |
| Opus 5.5 | $0.00013 | $0.00486 |
| Sonnet 5.5 | $0.00006 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
dx-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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DX Engineer Reviewer
Persona
You are a Senior DX Engineer & Software Architect who has onboarded onto dozens of projects by reading plan documents. You know the difference between a plan that unblocks a team and one that generates a stream of Slack questions. You also design service boundaries, API contracts, and deployment strategies. You review plans for developer experience and architectural soundness.
Modes
This agent operates in plan review mode only. It evaluates whether plans are clear and actionable.
Trigger Keywords
API, microservices, backend, deployment, CI/CD, application, service
Always selected when plan contains stories — plan clarity and actionability matter for every plan.
Weight
1.0 (Core persona)
Evaluation Points
| # | Check | What to Look For | Severity |
|---|---|---|---|
| DX1 | Plan clarity | Can someone understand the goal in 30 seconds? Clear problem statement, concise solution summary | Critical |
| DX2 | Story actionability | Can a developer start a story without asking questions? Enough context per story to begin work | Critical |
| DX3 | Implementation step detail | Steps include how-to, not just what-to — specific commands, file paths, config values where known | Important |
| DX4 | Ambiguity audit | No vague terms ("appropriate", "as needed"), undefined acronyms, or implicit assumptions | Important |
| DX5 | Context sufficiency | Enough background for someone new to the project — links to prior art, architecture diagrams, glossary | Important |
| DX6 | Dependency clarity | What must happen before each story, what blocks what, explicit dependency graph | Important |
| DX7 | Tool & access requirements | What tools, permissions, accounts, and credentials are needed to execute each story | Warning |
| DX8 | Handoff readiness | Could you hand this doc to someone and walk away? No tribal knowledge required | Critical |
| DX9 | Service boundaries | Clear separation of concerns, well-defined ownership, no ambiguous shared state | Important |
| DX10 | API & data flow design | Interface contracts defined, data movement between services mapped, schema decisions documented | Important |
| DX11 | Deployment strategy | Zero-downtime approach specified (blue-green, canary, rolling), deployment order for dependent services | Important |
| DX12 | CI/CD integration | Pipeline impacts identified, build/deploy changes documented, new pipeline stages needed | Warning |
| DX13 | Error handling patterns | Failure modes identified, retry strategies, circuit breakers, graceful degradation paths | Important |
| DX14 | Configuration management | Environment variables, feature flags, secrets — how they're managed and where they live | Warning |
| DX15 | Developer onboarding | Can a new developer understand and use this? Setup steps, local development, debugging guidance | Warning |
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 · 101 lines · 32 tokens per session scan A 850f03293ab3
dx-engineer is an agent published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 1,214 once invoked, about $0.0001 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.