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 instructions/lookatitude/guild/agents-mdgit 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.04819 | $0.04819 |
| Opus 5 | $0.02410 | $0.02410 |
| Sonnet 5 | $0.00964 | $0.00964 |
| Haiku 4.5 | $0.00482 | $0.00482 |
Grade A, and why
guild AGENTS.md 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guild — repo orientation
Guild is a cross-host plugin that ships 3 machinery agents (advisor, context-manager,
developer),
15 domain specialist type templates (minted into a project's .guild/agents/ on
demand by team composition), and 111 skills across a
brainstorm-plan-execute-review-verify-reflect spine, a categorized wiki with decision
capture, and a self-evolution loop with shadow-mode gating.
This AGENTS.md file is the canonical host-neutral instruction file. Claude Code
loads CLAUDE.md, but CLAUDE.md must only import this file; all durable
directions belong here so Codex, Pi, Antigravity, and AGENTS.md-consuming hosts
read the same guidance.
For full architecture and design documentation see https://guildstack.dev/docs.
Where things live
.claude-plugin/plugin.json,.claude-plugin/marketplace.json— plugin + marketplace manifests.skills/{core,meta,knowledge,specialists,guild-operations,guild-quality}/— skill taxonomy. The formerfallback/tier no longer exists — its skills were promoted intometa/(tdd,systematic-debug,worktrees,finish-branch) or folded intoguild:review.agents/*.md— the 3 machinery agents (advisor,context-manager,developer), the only host-registered agents the plugin ships. Populated and authored.templates/specialists/*.md— the 15 domain specialist type templates (guild.specialist_template.v1; architect … sales, incl.doc-writer), read-only feedstock minted into a project's.guild/agents/byroster-resolve.ts mintduring team composition.commands/*.md— the v2 flat-token command surface (/guild:<verb>; the:plugin namespace stays — Claude Code requires it — v2 only drops the redundantguild-prefix; sub-verbs are positional arguments, never separate files or namespaces).hooks/hooks.json— native Claude Code hooks; the.tssources compile to the committed esbuild bundles underhooks/dist/(+hooks/agent-team/dist/) the host actually runs (cd hooks && npm run buildafter any hook edit — source edits are a no-op until rebuilt). Other hosts consume equivalent behavior through host adapters and graceful fallback.src/modules/<module>/— the module source-of-truth layer. Each module owns itsworkflows/code plus aresources/mirror that generated host packages copy from;scripts/lib/*are thin re-export shims over these workflows. The module-resource sync (syncModuleResources) + drift gates keep the live surface, theresources/mirror, and the per-hostdist/copies byte-identical. Edit the live source (scripts/lib,src/modules/*/workflows,hooks/*.ts); never hand-edit aresources/ordist/mirror — run the sync + host-package build to propagate.scripts/,mcp-servers/— evolve loop, telemetry, optional MCP servers.dist/— committed per-host packages (claude-code,codex,pi, …) rendered byscripts/build-host-packages.ts; regenerated, never hand-edited.tests/— skill evals and wiki-lint fixtures.templates/{skills,agents,products}/— authoring + product scaffolds (templates/specialists/is the 15 specialist type templates, described above).docs/— RETIRED as a docs set: holds only a static redirect page tohttps://guildstack.dev/docsplus the logo asset. The public docs are generated from the umbrella'sdocs/v2/+ the website; reference knowledge lives in.guild/wiki/. Apart fromREADME.md,CONTRIBUTING.md, andCHANGELOG.md, no documentation lives in this repo.
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 · 314 lines · 4,819 tokens per session scan A 6bbd92b6b02b
guild AGENTS.md is an instructions file published in the GitHub repository lookatitude/guild (7 stars, last pushed 2d ago), licensed MIT. It adds 4,819 tokens to every session, about $0.0241 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 instructions, from other repositories
spellbook AGENTS.md
Instructions for majiayu000/spellbook, covering spellbook agent contract, routing, scope rules, threads long-run guardrails and validation.
open-supermarkets AGENTS.md
Instructions for abracadabra50/open-supermarkets, covering agent integration guide, supported frameworks, quick integration, 1. add as skill and 2. agent calls commands.
helm copilot-instructions.md
Instructions for PetePeter/helm, covering gamepad-cli-hub — copilot instructions, project purpose, system overview, data flow pipeline and key controls.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
fusion-skills AGENTS.md
AGENTS.md instructions for CrowdStrike/fusion-skills, covering agents.md, what this is, prerequisites, repository structure and skills ecosystem.
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).