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/plan)<a href="https://agentmods.dev/commands/infraspecdev/tesseract/plan"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/plan/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/plan"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/plan.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.00029 | $0.02761 |
| Opus 5.5 | $0.00012 | $0.01104 |
| Sonnet 5.5 | $0.00006 | $0.00552 |
| Haiku 4.5 | $0.00003 | $0.00276 |
Grade A, and why
plan 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan
Generate Shield plan documents with a machine-readable sidecar.
Usage
/plan [--name <plan-name>] [topic or requirements]
Paths
This command writes the following registry-tracked paths (see shield/schema/output-paths.yaml):
| Registry key | Resolved path |
|---|---|
plan_json |
{output_dir}/{feature}/plan.json |
plan_md |
{output_dir}/{feature}/plan.md |
plan_trd_md |
{output_dir}/{feature}/trd.md |
plan_html |
{output_dir}/{feature}/outputs/plan.html |
plan_trd_html |
{output_dir}/{feature}/outputs/trd.html |
prd_meta_json |
{output_dir}/{feature}/prd.meta.json (updated — appends to linked_plans) |
lld_draft_md |
{output_dir}/{feature}/lld-{component}.md (one per lld_components[] entry; canonical docs/lld/ is untouched at /plan time) |
The global dashboard {output_dir}/index.html (registry key global_index_html) is updated as a side effect; it is not declared in outputs: because it is a cross-feature artifact, not a per-run deliverable.
Legacy keys: plan_arch_md and plan_arch_html are deprecated and no longer written by /plan. They remain in the registry with deprecated: true so older folders containing a plan-architecture.md stay readable. /plan never deletes or modifies an existing plan-architecture.md — see "Re-run behavior" below.
Output Paths — MANDATORY
First, find the project root by locating .shield.json (check current directory, then parent directories). Read the output_dir field from .shield.json (default: docs/shield if not set). Then write each artifact using the Write tool to:
{project_root}/{output_dir}/{feature}/plan.json— machine-readable sidecar (registry:{plan_json}){project_root}/{output_dir}/{feature}/plan.md— canonical detailed plan markdown (registry:{plan_md}){project_root}/{output_dir}/{feature}/trd.md— canonical 14-section Technical Requirements Document (registry:{plan_trd_md}){project_root}/{output_dir}/{feature}/outputs/plan.html— rendered detailed plan HTML (registry:{plan_html}){project_root}/{output_dir}/{feature}/outputs/trd.html— rendered TRD HTML (registry:{plan_trd_html}){project_root}/{output_dir}/index.html— single dashboard linking to all artifacts (create or update; cross-feature side-effect)
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 · 145 lines · 29 tokens per session scan A 8397e8eaa9ac
plan is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 2,761 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.