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/monkey1wizard/golem-agents-legion/agents-mdgit clone --depth 1 https://github.com/monkey1wizard/Golem-Agents-LegionWrote 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/instructions/monkey1wizard/golem-agents-legion/agents-md)<a href="https://agentmods.dev/instructions/monkey1wizard/golem-agents-legion/agents-md"><img src="https://agentmods.dev/badge/instructions/monkey1wizard/golem-agents-legion/agents-md.svg" alt="Measured on agentmods" 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 | $0.02129 | $0.02129 |
| Opus 5 | $0.01064 | $0.01064 |
| Sonnet 5 | $0.00426 | $0.00426 |
| Haiku 4.5 | $0.00213 | $0.00213 |
Grade A, and why
Golem-Agents-Legion 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 today.
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Golem-Agents-Legion GEMINI.md — 94% identical, 4 lines differ
- Golem-Agents-Legion CLAUDE.md — 89% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generated by
/gal initfor Codex CLI, Copilot CLI, Antigravity workspace rules, remaining Google CLI bridges, and opencode. Do not edit manually.
GAL Agent Instructions
Named Workflow Obedience
Binding. When the user invokes any GAL named workflow — $gal-pipeline, $gal-finalize, $gal-status, $deep-planning, $refining-plan, $plan-to-prompt — or expresses repo-work intent (implement, plan, finalize, review, 實作, 規劃, 跑 pipeline, finalize), your first action MUST be to load and execute the corresponding SKILL.md before taking any action. Generic autonomous coding, batch edits, or a summary response that bypasses the named workflow is a named workflow obedience failure.
Critical Stop Rules
The GAL critical runtime pack — binding stop rules for headless and interactive runs alike:
$gal-pipeline: the first implementation edit is gated ongal pipeline-preflight <prompt> --receipt <path>returningpass— make no edit before that.- When more than one plan is active, require an explicit
'#file:<prompt>'path. Never auto-select the first active-plan row. - If a receipt/log write fails under sandbox denial, STOP and rerun the exact
galcommand after approval — do not fall back to role-playing pipeline phases in chat. - The goal-backward verify pass is orchestrator-owned and always runs in-process. It is never a dispatch phase.
Working Hours
Interactive/chat work and direct golem calls honor Wrap-up Time and Hard Stop when enabled. /gal pipeline execution itself is exempt. Read plugins/gal-core/conventions/working-hours.md for the current rule before assuming either state.
Cold Start Order
.dev/project.md2..dev/state.md3. the active plan's*.prompt.md, resolved via the.dev/state.mdActive Plans row — never a hardcoded transient filename 4.docs/manual.md/plugins/gal-core/workflows/coding.mdonly when the current task needs them.
Repo Skills
The following repo-local skills are available by name. Read the corresponding skills/<name>/SKILL.md file when full instructions are needed.
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.
- today First seen · 135 lines · 2,129 tokens per session scan A 4b6204d20079
Golem-Agents-Legion AGENTS.md is an instructions file published in the GitHub repository monkey1wizard/Golem-Agents-Legion (15 stars, last pushed 2d ago), licensed MIT. It adds 2,129 tokens to every session, about $0.0106 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-09-04.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).