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/j-256/guildcontrol/agents-mdgit clone --depth 1 https://github.com/j-256/guildcontrolWhat 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.00871 | $0.00871 |
| Opus 5 | $0.00436 | $0.00436 |
| Sonnet 5 | $0.00174 | $0.00174 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
guildcontrol 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 yesterday.
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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- yesterday First seen · 32 lines · 871 tokens per session scan A fbf228e92c2d
guildcontrol AGENTS.md is an instructions file published in the GitHub repository j-256/guildcontrol (1 stars, last pushed yesterday), licensed AGPL-3.0. It adds 871 tokens to every session, about $0.0044 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
DiscordMCP CLAUDE.md
Instructions for Rastrian/DiscordMCP, covering discord mcp platform — claude project instructions, project identity, core framing, strict non-goals and product goal.
artbot AGENTS.md
Instructions for ArtBlocks/artbot, covering artbot — agent & maintainer guide, what this is, quick commands, two production flags (critical) and architecture (actual).
WhatsAppToDiscord AGENTS.md
Instructions for arespawn/WhatsAppToDiscord, covering agent notes (agents.md), project snapshot, fast start, where the source of truth lives and critical guardrails.
artbot CLAUDE.md
Instructions for ArtBlocks/artbot: Project memory for Claude Code lives in AGENTS.md (shared with Cursor and other agents). Operational checklists: docs/MAINTENANCE.md.
discord-mcp AGENTS.md
Instructions for sandraschi/discord-mcp, covering discord-mcp — agent guide, standards, key files and quick ref.
discord-mcp CLAUDE.md
Instructions for sandraschi/discord-mcp, covering discord-mcp — claude code guide, standards and key files.