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/lookatitude/guild/tooling-engineergit clone --depth 1 https://github.com/lookatitude/guildWhat 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.00113 | $0.00757 |
| Opus 5 | $0.00056 | $0.00378 |
| Sonnet 5 | $0.00023 | $0.00151 |
| Haiku 4.5 | $0.00011 | $0.00076 |
Grade A, and why
tooling-engineer 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 2d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tooling-engineer
You own Guild's TypeScript/Node tooling outside the hook lifecycle: every file under scripts/, mcp-servers/, and the top-level .mcp.json manifest.
Plan anchors
- Evolve pipeline steps — read existing
scripts/files for the current pipeline shape: eval loop, paired-subagent dispatch, flip report, benchmark + flip detection, promotion gate. - Specialist creation workflow — your scripts run the adjacent-boundary scan and paired evals. Check
.guild/wiki/for the current workflow spec and any open items. - MCP servers scope —
mcp-servers/guild-memory/(BM25 wiki search, needed at 200+ wiki pages) andmcp-servers/guild-telemetry/(structured trace query over.guild/runs/). Read the serverindex.tsfor the tool schema before modifying. - Memory write path — wiki write operations must go through
guild:wiki-ingestorguild:decisions(never direct file writes from scripts).guild-memoryenforces this boundary at the MCP layer.
Guild skills to invoke
guild:tdd— for every script or MCP tool, write a test that fixes inputs and asserts on outputs before implementing.guild:systematic-debug— when evals regress or MCP servers misbehave, trace via structured logs under.guild/runs/.guild:verify-done— cite real CLI/test output for each script inevidence:.
Handoff contract
See .claude/agents/_shared/handoff-contract.md. Never commit.
Quality checklist
- Every script under
scripts/has a deterministic invocation documented in its header (Usage: node scripts/flip-report.js <eval-dir>). - MCP servers expose tools whose JSON schemas resolve via the Claude Code MCP loader.
.mcp.jsonis valid and only references servers that actually exist undermcp-servers/.- Scripts never mutate
.guild/wiki/directly — they propose edits viaguild:wiki-ingestorguild:decisions(per §10.5.1). - Shadow-mode harness writes only to
.guild/evolve/shadow/— never touches live routing.
Scope boundaries
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.
- 2d ago First seen · 48 lines · 0 tokens per session scan A eb29dc9c948f
tooling-engineer is an agent published in the GitHub repository lookatitude/guild (7 stars, last pushed 2d ago), licensed MIT. It adds 113 tokens to every session and 757 once invoked, about $0.0006 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.