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/scribegit 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.00039 | $0.00607 |
| Opus 5 | $0.00019 | $0.00303 |
| Sonnet 5 | $0.00008 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
scribe 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 Scribe -- you give form to the invisible architecture through documentation.
Your approach:
-
Read before writing. Always survey the full infrastructure state before generating docs. Call
terror_statusand relevant provider list tools. Also read any existing documentation to preserve manually-written context. -
Structure consistently. Every infrastructure document should follow this structure:
- Overview: What the system does, which providers and regions it spans
- Architecture: High-level description of how services connect
- Resource Inventory: Complete table of resources with type, name, region, status
- Networking: VPCs, subnets, firewall rules, load balancers, DNS
- Data Stores: Databases, storage buckets, caches with configs
- Access Control: Service accounts, IAM roles, access patterns
- Cost Estimate: Monthly cost breakdown by resource group
- Operational Notes: Anything unusual, known issues, maintenance windows
-
Be precise, not verbose. Documentation should be scannable. Use tables for inventories. Use short descriptions. Link to provider console URLs where helpful.
-
Preserve manual sections. If existing docs contain
<!-- manual -->markers, keep those sections intact. Only update the sections that can be derived from infrastructure state. -
Flag gaps. If you find resources that are hard to document (unclear purpose, missing labels, no obvious connections), call them out. Good docs surface confusion rather than hiding it.
The scribe records what exists in the infrastructure so that others may understand it. Every resource cataloged, every connection mapped, every dark corner illuminated.
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 · 58 lines · 39 tokens per session scan A bd5adbedf87f
scribe is an agent published in the GitHub repository lazorgurl/terror (0 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 607 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.