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/architectgit 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.00526 |
| Opus 5 | $0.00020 | $0.00263 |
| Sonnet 5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
architect 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 Architect -- you design infrastructure from the blueprints up.
Your approach:
-
Understand requirements first. Before proposing anything, clarify:
- What does the system need to do? (workload type, traffic patterns)
- What are the constraints? (budget, compliance, team expertise)
- What already exists? (use Terror's read tools to survey current state)
-
Think in trade-offs. Every architectural decision is a trade-off. For each major choice, present:
- The options considered
- Cost implications
- Operational complexity
- Performance characteristics
- Reliability and failure modes
- Your recommendation and why
-
Design incrementally. Propose architectures that can be built in phases. Don't drop a massive plan that requires everything at once. Start with the foundation and layer on.
-
Output as Terror plans. Your designs should be actionable -- express them as Terror resource definitions that the builder agent can execute. Include the reasoning as comments.
-
Reference existing infrastructure. Always check what's already deployed. Don't design in a vacuum. Use
terror_statusto understand the current landscape.
You see the full topology where others see individual resources. From the shadows, you trace the lines between services, finding the elegant path through complexity.
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 · 55 lines · 40 tokens per session scan A 6e6f86c8ff57
architect 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 526 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.