agentmods.dev

inspect

A command for making a detailed inventory of cloud infrastructure managed by Terror and mapping how its resources connect.

In plain words
What is it for?
Use it to inspect compute, storage, databases, networking, and access permissions across supported providers, then review relationships and detected issues.
Why use it?
It can reveal unhealthy or wasteful resources, risky access permissions, missing labels, public storage, and unexpected locations.

Command for Claude Code

0 5mo ago A scan 15 tokens original MIT
View the source file lazorgurl/terror
Install

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.

agentmods
npx agentmods add commands/lazorgurl/terror/inspect
Clone the repo
git clone --depth 1 https://github.com/lazorgurl/terror

Made for: Claude Code.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 340 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00340
Opus 5 $0.00008 $0.00170
Sonnet 5 $0.00003 $0.00068
Haiku 4.5 $0.00002 $0.00034

Measured yesterday against content hash a31b69ada894, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

inspect 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.

.claude/plugins/terror/commands/inspect.md · 42 lines

What it actually says

Inspect Infrastructure

Perform a thorough inspection of all managed infrastructure.

Steps

  1. Inventory. Call terror_status to list all managed resources. Group by:

    • Provider (GCP, AWS, Azure)
    • Type (compute, storage, database, networking, IAM)
    • Environment (production, staging, dev)

  2. Resource details. For each resource group, use provider-specific list tools:

    • gcp_compute_list, aws_ec2_list for compute
    • gcp_storage_list, aws_s3_list for storage
    • gcp_iam_list, aws_iam_list for IAM Show key attributes: state, region, creation date, tags/labels.

  3. Relationship mapping. Identify how resources connect:

    • Which compute instances talk to which databases
    • Load balancer targets
    • VPC/subnet membership
    • IAM bindings and service accounts

  4. Issue detection. Flag potential problems:

    • Unattached disks or elastic IPs (wasted cost)
    • Overly permissive IAM roles (security risk)
    • Public storage buckets without explicit justification
    • Resources missing tags or labels
    • Instances running in default VPC
    • Resources in unexpected regions

  5. Present findings. Organize output as:

    • Resource inventory table
    • Relationship summary
    • Issues found, ranked by severity (critical / warning / info)
    • Recommended actions for each issue
Changes

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.

  1. yesterday First seen · 42 lines · 15 tokens per session scan A a31b69ada894

Subscribe to this mod's changes

inspect is a command published in the GitHub repository lazorgurl/terror (0 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 340 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.

Code review
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

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.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

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.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens