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 AlexK020908/infra-designer/plugin install infra-designerWrote 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/alexk020908/infra-designer/research-component)<a href="https://agentmods.dev/commands/alexk020908/infra-designer/research-component"><img src="https://agentmods.dev/badge/commands/alexk020908/infra-designer/research-component/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/alexk020908/infra-designer/research-component"><img src="https://agentmods.dev/badge/commands/alexk020908/infra-designer/research-component.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.00416 |
| Opus 5 | $0.00019 | $0.00208 |
| Sonnet 5 | $0.00008 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
research-component 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 9d 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.
What it actually says
Research a component from docs
The user wants to grow the registry from authoritative documentation. Their request (expected to contain a documentation URL, optionally with a description of the component):
$ARGUMENTS
How to run this
-
If no URL is present, ask the user for the documentation link before doing anything — this command is doc-driven; don't research from memory.
-
Confirm it's actually missing. Run
python ${CLAUDE_PLUGIN_ROOT}/engine/cli.py listand skim${CLAUDE_PLUGIN_ROOT}/components/<provider>/. If an existing component already covers the capability, say so and stop rather than adding a duplicate. -
Use the
research-componentskill (skills/research-component/SKILL.md) to do the deep research: crawl the supplied page, triage its links, fan out subagents in parallel over the relevant subpages (argument reference, IAM/auth, limits, pricing), and synthesize a verified research brief. Requires web access — if you don't have it, list what you'd need to verify and stop; never invent a provider schema. -
The skill hands the brief to the
author-componentskill to write the four-file component, register it (cli.py index), add it toknowledge/freshness.json, and validate it with a clean render. -
Report the new
type, the files written, the sources crawled (and subagent count), anything left unverified with the conservative default chosen, and the render result. The component is now usable in/plan-infraand anyinfra/<project-name>/spec.json.
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.
- 9d ago First seen · 35 lines · 39 tokens per session scan A ec3cbab7eca1
research-component is a command published in the GitHub repository AlexK020908/infra-designer (2 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 416 once invoked, about $0.0002 per session on Opus 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 commands, from other repositories
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
init
Generate FILETREE.md from scratch. Confirms overwrite if it already exists. --self-only keeps every artifact out of git.
uninstall
Uninstall filetree from this repo — un-wires CLAUDE.md/AGENTS.md, removes generated artifacts (confirmed per item), tears down self-only mode if enabled.
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.