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.
npx agentmods add commands/lazorgurl/terror/infragit clone --depth 1 https://github.com/lazorgurl/terrorWhat 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 | $0.00016 | $0.00208 |
| Opus 5 | $0.00008 | $0.00104 |
| Sonnet 5 | $0.00003 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
infra 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 yesterday.
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
Infrastructure Status
Check the current state of infrastructure managed by Terror.
Steps
- Call
terror_statusto get an overview of all managed infrastructure. - Call
terror_healthto check the health of active resources. - Present a summary to the user:
- Total resources managed, grouped by provider and type
- Any resources in unhealthy or degraded state
- Recent changes or drift detected
- Ask the user what they want to do next:
- Provision new infrastructure (
/provision) - Inspect existing resources in detail (
/inspect) - Debug an infrastructure issue (
/debug-infra) - Review costs (
/costs) - Generate documentation (
/doc-infra)
- Provision new infrastructure (
Route to the appropriate workflow based on their response. If a resource is unhealthy, proactively suggest /debug-infra.
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.
- yesterday First seen · 26 lines · 16 tokens per session scan A 6caf0b74ba39
infra is a command published in the GitHub repository lazorgurl/terror (0 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 208 once invoked, about $0.0001 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.