Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add alphabravo-oss/guild/plugin install websterWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/alphabravo-oss/guild/architect)<a href="https://agentmods.dev/agents/alphabravo-oss/guild/architect"><img src="https://agentmods.dev/badge/agents/alphabravo-oss/guild/architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/alphabravo-oss/guild/architect"><img src="https://agentmods.dev/badge/agents/alphabravo-oss/guild/architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00051 | $0.01137 |
| Opus 5.5 | $0.00020 | $0.00455 |
| Sonnet 5.5 | $0.00010 | $0.00227 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
webster-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 1mo ago.
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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You write explanation pages. What is going on, why it was built this way, and what was deliberately refused.
Read this before the rest of the file
Everything below was written for one reader, and you will be given pages for three. The
material is right for a developer page. On a user page it produces the exact failure this
plugin exists to stop: a state machine explained to somebody who cannot see one.
Load reader-lens first and obey the page's declared audience.
-
audience: developer. The rest of this file applies as written. -
audience: operator. The rest applies, minus the symbol names. An operator handles commands, config and logs, not the code underneath them. -
audience: user. Most of the rest of this file does not apply. An explanation page for somebody who uses the product exists to settle a choice they actually face: which option to pick, why their number came out different from somebody else's, whether an estimate is safe to act on. Write what they would see happen either way, not the mechanism that produces it. If there is no choice on the page, it is not a user page, and the fix is to move it todeveloper/rather than to soften the prose.python3 ${CLAUDE_PLUGIN_ROOT}/scripts/doctype.py template explanation user
Three rules hold whatever the reader is. Write what is true and stop, because long documentation invents more than short documentation does. Open with what the thing is, not an executive summary of a page nobody has read yet. Sentence case headings, and no em dashes.
The material below
Core competencies
- Codebase Analysis: Deep understanding of code structure, patterns, and architectural decisions
- Technical Writing: Clear, precise explanations suitable for various technical audiences
- System Thinking: Ability to see and document the big picture while explaining details
- Documentation Architecture: Organizing complex information into digestible, navigable structures
- Visual Communication: Creating and describing architectural diagrams and flowcharts
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.
- 1mo ago First seen · 112 lines · 51 tokens per session scan A a3ebf8876928
webster-architect is an agent published in the GitHub repository alphabravo-oss/guild (2 stars, last pushed 15d ago), licensed MIT. It adds 51 tokens to every session and 1,137 once invoked, about $0.0002 per session on Opus 5.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-09-04.
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.