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/research)<a href="https://agentmods.dev/commands/infraspecdev/tesseract/research"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/research/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/research"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/research.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.00039 | $0.00645 |
| Opus 5.5 | $0.00016 | $0.00258 |
| Sonnet 5.5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
research 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paths
This command writes the following registry-tracked paths (see shield/schema/output-paths.yaml):
{research}→{output_dir}/{feature}/research.md
Side-artifact (not declared in outputs:):
.session-transcript.md→{output_dir}/{feature}/.session-transcript.md
/research
Two-phase research command. Phase 1 captures internal context via Q&A + repo scan. Phase 2 (opt-in) runs external evidence-gathering on open questions.
Usage
/research <topic> # interactive — both phases offered
/research --lean <topic> # use lean depth mode (5 topics only)
/research --deep <topic> # use deep depth mode (~15 topics)
/research --phase2-only # skip Phase 1, run only external evidence-gathering (legacy behavior)
What it does
Phase 1 (new)
- Silent repo scan — detects Stack, Integrations, Compliance markers, Deployment pattern, Recent activity, ADRs, Prior research artifacts
- Confirm detected context with user — yes / no / correct / add
- Q&A walk — asks product + tech topics, skipping any auto-answered from invocation message, repo scan, or prior transcript
- Surface open questions + offer Phase 2
Phase 2 (existing — opt-in after Phase 1)
- PM framing on chosen questions
- 3 parallel agents — official sources, industry voices, community experience
- Synthesize with citations
- PM review on synthesis
- Write
{research}(research.md) with sourced evidence
Output
{output_dir}/{feature}/
├── research.md # {research} — findings (always present if Phase 2 ran) or Phase 1 context
└── .session-transcript.md # hidden side-artifact — Phase 1 Q&A + repo scan context (always written)
Numbered run subfolders (
research/{N}-{slug}/) no longer exist. Git history is the archive.
Reference
Full behavior in shield/skills/general/research/SKILL.md. See repo-scan.md for detection rules and qa-topics.md for the topic catalog.
See also
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 · 69 lines · 39 tokens per session scan A e1c8d8a07bfb
research is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 645 once invoked, about $0.0002 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.