Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add infraspecdev/tesseract/plugin install shieldWrote 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/migrate)<a href="https://agentmods.dev/commands/infraspecdev/tesseract/migrate"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/migrate/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/migrate"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/migrate.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.00025 | $0.02989 |
| Opus 5.5 | $0.00010 | $0.01196 |
| Sonnet 5.5 | $0.00005 | $0.00598 |
| Haiku 4.5 | $0.00003 | $0.00299 |
Grade A, and why
migrate 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shield Migrate
Detect and migrate configuration and plan artifacts from old Tesseract plugins to the Shield structure.
Phase 1: Detect
Scan for old plugin artifacts:
sprint-planner.json→ ClickUp config (clickup-sprint-planner plugin)phases/directory with HTML plan docs → plan artifactsreview/directory with analysis/plan markdown → review artifactsclaude/infra-review/directory → infra-review was activeshield/plan.json(old single-plan path) → needs migration to{output_dir}/{feature}/plan.json
Report findings:
Detected old plugin artifacts:
- sprint-planner.json (ClickUp config with 7 epics)
- phases/ (7 phase directories with architecture.html + detailed-plan.html)
- review/ (1 review: 2026-03-12-eks-foundation)
If nothing detected, suggest /shield init instead.
Phase 2: Migrate Config
-
Gather project info:
- Ask for project name (default: repo directory name)
- Infer domains from content (HTML plan docs with Terraform →
terraform) - Ask user to confirm/adjust
-
Create
.shield.jsonwith confirmed project name,output_dir(ask user, default:docs/shield), and domains. Add gitignore patterns for ephemeral review output (same as/shield initstep 4). -
Migrate sprint-planner.json (if found):
Old field New location clickup.space.id~/.shield/projects/<project>/pm.json→space_idclickup.folder.id~/.shield/projects/<project>/pm.json→workspace_idclickup.lists.backlog.id~/.shield/projects/<project>/pm.json→ used by pm-syncclickup.relationship_field~/.shield/projects/<project>/pm.json→ preservednaming.*~/.shield/projects/<project>/pm.json→naming.*CLICKUP_API_TOKENenv var~/.shield/credentials.json→clickup.api_token- Set
adapter: "clickup"andadapter_mode: "hybrid"in pm.json - Register the PM adapter MCP server:
- Read
${CLAUDE_PLUGIN_ROOT}/adapters/clickup/.mcp.jsonto get the server entries - Merge those entries into
${CLAUDE_PLUGIN_ROOT}/.mcp.json→mcpServersobject
- Read
- Set
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 · 249 lines · 25 tokens per session scan A 372c623f66ef
migrate is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 2,989 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.