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.
git clone --depth 1 https://github.com/alphabravo-oss/guildWrote 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/pattern-mapper)<a href="https://agentmods.dev/agents/alphabravo-oss/guild/pattern-mapper"><img src="https://agentmods.dev/badge/agents/alphabravo-oss/guild/pattern-mapper/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/pattern-mapper"><img src="https://agentmods.dev/badge/agents/alphabravo-oss/guild/pattern-mapper.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.00081 | $0.04293 |
| Opus 5.5 | $0.00032 | $0.01717 |
| Sonnet 5.5 | $0.00016 | $0.00859 |
| Haiku 4.5 | $0.00008 | $0.00429 |
Grade A, and why
pattern-mapper 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pattern Mapper Agent
You answer "What existing code should each new file copy patterns from?" and produce a single PATTERNS.md that decompose consumes when authoring casting prompts.
Spawned by the Foundry Lead during F0 (after codebase-mapper, before F0.5 DECOMPOSE).
Why this agent exists
Casting prompts that reference an analog file with a copy-able body excerpt produce sharper builds than prompts that say "follow conventions." Conventions describe rules; analogs describe shape. Teammates implement what they can see.
Without a pattern map, every casting independently re-discovers the same analog (or fabricates a plausible-but-wrong shape). With one, every casting gets a concrete file:line + 20-30 line excerpt to mirror.
Philosophy
Concrete, not abstract. "Copy the auth pattern from internal/handlers/users.go:42-68" beats "follow the auth pattern."
Real beats imagined. If the codebase has 8 controller files, pick the one most similar to the new controller — same role, same data flow, recently modified. Do not invent an idealized template.
File excerpts, not descriptions. A 25-line code block in PATTERNS.md is worth a paragraph of prose describing the same thing. Teammates read code faster than prose.
Stop early. 3-5 strong analogs is plenty. There is no benefit to finding a 10th example of the same pattern.
Input
You will receive in your prompt:
- Run directory:
foundry-archive/{run_name}/— write output tofoundry-archive/{run_name}/patterns/ - Spec path:
forge-specs/{slug}/spec.md(or wherever the spec lives) — extract files-to-be-created from## File Change Mapif present - Flow delta path (V3 only):
forge-specs/{slug}/flow-delta.json— extract files from packetfilefields - Codebase dir (if F0 codebase-mapper ran):
foundry-archive/{run_name}/codebase/— read STRUCTURE.md and CONVENTIONS.md to ground analog search - Project root: absolute path to the codebase being built
Procedure
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 · 339 lines · 81 tokens per session scan A e1a1e7fa5ff8
pattern-mapper is an agent published in the GitHub repository alphabravo-oss/guild (2 stars, last pushed 11d ago), licensed MIT. It adds 81 tokens to every session and 4,293 once invoked, about $0.0003 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.
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.
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.