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/commands/infraspecdev/tesseract/implement)<a href="https://agentmods.dev/commands/infraspecdev/tesseract/implement"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/implement/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/commands/infraspecdev/tesseract/implement"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/implement.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.00011 | $0.00624 |
| Opus 5.5 | $0.00004 | $0.00250 |
| Sonnet 5.5 | $0.00002 | $0.00125 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
implement 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement
Start implementing a feature using test-driven development with progress tracking.
Usage
/implement [feature or story ID]
Paths
This command mutates {plan_json} = {output_dir}/{feature}/plan.json in place as steps complete. On milestone close (step 5h), it also promotes feature-folder LLD drafts to the canonical docs/lld/{component}.md location (registry: lld_canonical_md).
| Registry key | Resolved path | When written |
|---|---|---|
plan_json |
{output_dir}/{feature}/plan.json |
Mutated in place on every story-status change |
lld_canonical_md |
docs/lld/{component}.md |
Promoted from {output_dir}/{feature}/lld-{component}.md at milestone close (step 5h) |
Behavior
- If a story ID is provided (e.g., EPIC-1-S1), search all plans in
{output_dir}/*/plan.jsonfor the story - If a feature description is provided, use it as the starting context
- If nothing provided, ask what the user wants to implement
Acceptance Criteria Confirmation
- If story context exists (from sidecar or PM tool):
- Present acceptance criteria to the user
- Ask to confirm, edit, or skip
- If edited, update
{plan_json}and re-render{plan_html}from the updated{plan_md}(via the/planrendering flow)
Implementation
- Follow the
shield:implement-featureskill workflow:- TDD: write failing tests, implement, per-step review
- Commit after each step
- Update story status in
{plan_json}={output_dir}/{feature}/plan.json
- On the story close that completes a milestone, promote each LLD draft
listed in
plan.json milestones[<M>].touches_lld[]fromdocs/shield/{feature}/lld-{component}.mdtodocs/lld/{component}.md. This includes a fork-drift concurrency check, §14 Changelog row append, atomic rename, anddesign_refs[]anchor back-fill. See step 5h inshield:implement-feature/SKILL.mdfor the full procedure and the just-in-time auto-heal rules. - If superpowers is available, delegate TDD to
superpowers:test-driven-development - After all steps complete, invoke
shield:summarize
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 · 59 lines · 11 tokens per session scan A 883943be19e1
implement is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 624 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.