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/guild-agents/guild/claude-mdgit clone --depth 1 https://github.com/Guild-Agents/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.01440 | $0.01440 |
| Opus 5 | $0.00720 | $0.00720 |
| Sonnet 5 | $0.00288 | $0.00288 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade A, and why
guild CLAUDE.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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
guild
Framework
This project uses Guild. A SessionStart hook injects a brief recap of the previous session automatically — no manual session file. Use /resume or claude --continue to reopen a prior conversation in full.
Stack
npm, chalk, clack, claude code, node, javascript
Project structure
bin/guild.js # CLI entry point (Commander.js)
src/
commands/ # CLI commands (one file per command)
init.js # guild init — interactive onboarding
new-agent.js # guild new-agent <name>
status.js # guild status
doctor.js # guild doctor — setup verification
list.js # guild list — agents & skills
__tests__/ # Co-located tests (*.test.js)
utils/ # Shared utilities
files.js # File I/O, template copying, frontmatter parsing
generators.js # Generates CLAUDE.md, PROJECT.md
github.js # GitHub CLI (gh) integration
__tests__/ # Co-located tests
hooks/ # SessionStart recap hook (shipped in the plugin)
transcript-recap.mjs # Pure: transcript lines -> recap string
session-recap.mjs # IO shell: stdin -> previous transcript -> stdout
templates/ # Scaffolding templates copied to user projects
agents/*.md # Agent definitions (6 agents)
skills/*/SKILL.md # Skill definitions (8 skills)
hooks/hooks.json # Plugin hook manifest (SessionStart)
CLAUDE.md # Project instructions (enriched by guild-specialize)
PROJECT.md # Project identity and stack
.claude/agents/*.md # Active agent definitions
.claude/skills/*/SKILL.md # Active skill definitions
.github/workflows/ci.yml # CI: lint + test on Node 20.x, 22.x
.github/workflows/release.yml # Release: npm publish on v* tags
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 · 115 lines · 1,440 tokens per session scan A 58205e549b32
guild CLAUDE.md is an instructions file published in the GitHub repository Guild-Agents/guild (4 stars, last pushed 1mo ago), licensed MIT. It adds 1,440 tokens to every session, about $0.0072 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
pi-extensions AGENTS.md
Instructions for narumiruna/pi-extensions, covering repository guidelines, documentation and communication, repository structure, commands and tooling and dependency safety.
whoop-mcp CLAUDE.md
Instructions for shashankswe2020-ux/whoop-mcp, covering project: whoop-mcp, tech stack, commands, project structure and code conventions.
whoop-mcp copilot-instructions.md
Instructions for shashankswe2020-ux/whoop-mcp, covering project: whoop-mcp, tech stack, commands, code conventions and testing.
huly-mcp CLAUDE.md
Instructions for dearlordylord/huly-mcp, covering project instructions, design principle: llm-first api, project harness (copy to new projects), package manager and verification.
zapo CLAUDE.md
Instructions for vinikjkkj/zapo: The contributor handbook for this repository lives in AGENTS.md. Read that file and follow it as your primary source of project conventions, architecture rules, performance constraints, and review anti-patterns.
Silex AGENTS.md
AGENTS.md instructions for silexlabs/Silex, covering agents.md, tech stack, run it locally, building the desktop app and when writing code for silex (editing source).