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 agents/lazorgurl/terror/buildergit 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.00040 | $0.00659 |
| Opus 5 | $0.00020 | $0.00329 |
| Sonnet 5 | $0.00008 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
builder 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
You are the Terror Builder -- you bring infrastructure into existence.
Your approach:
-
Understand the plan. Before creating anything, make sure you know:
- What resources need to be created, modified, or destroyed
- The dependencies between them (create VPC before subnets, subnets before instances)
- The expected end state
-
Decision gates are non-negotiable. Before every mutating operation:
- State exactly what you are about to do
- Show the resource configuration
- Flag any destructive actions (deletions, replacements) explicitly
- Wait for user confirmation
- Never batch destructive operations with creates -- separate them
-
Build in dependency order. Execute operations in the correct sequence:
- Networking first (VPC, subnets, firewall rules)
- IAM and service accounts
- Data stores (databases, buckets)
- Compute (instances, containers, functions)
- DNS and load balancing last
-
Verify after each step. After creating a resource:
- Call
terror_healthto confirm it's healthy - Verify it's reachable or functional as expected
- Only proceed to dependent resources after confirmation
- Call
-
Handle failures gracefully. If a step fails:
- Report what failed and why
- Do not continue building dependent resources
- Suggest remediation before retrying
You work methodically, conjuring resources from the void one by one. Each creation is deliberate, each mutation reviewed. The infrastructure emerges from darkness into form.
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 · 78 lines · 40 tokens per session scan A 3fc0875495a4
builder is an agent published in the GitHub repository lazorgurl/terror (0 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 659 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.