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/runesleo/claude-code-workflow/agents-mdgit clone --depth 1 https://github.com/runesleo/claude-code-workflowWhat 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.00227 | $0.00227 |
| Opus 5 | $0.00113 | $0.00113 |
| Sonnet 5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
claude-code-workflow 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.
What it actually says
Repository Instructions
- This repository publishes a sanitized map of Leo's current AI work system: a small shared Core, nine business lines, task continuity, background boundaries, and open-source branches.
- Preserve the real topology and the reasons behind it. Do not flatten the project back into a generic workflow template.
- Keep always-loaded instructions short. Put explanations in docs and load them only when relevant.
- Never add absolute personal paths, live tasks, thread IDs, private state, credentials, accounts, positions, health records, customers, or production controls.
- Public examples may preserve real contracts and business-line names, but their task content and timestamps must be explicitly synthetic.
- Do not make plans, spawn agents, or add workflow artifacts for simple edits.
README.mdand default docs are the Chinese source language.README.en.mdand*.en.mdfiles are compatibility mirrors.- Any behavioral claim must match the files users actually install.
- Run
./scripts/verify.shbefore declaring a change complete. - Pushes, tags, releases, and public posts require the maintainer's explicit approval.
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 · 13 lines · 227 tokens per session scan A bcc835d89d76
claude-code-workflow AGENTS.md is an instructions file published in the GitHub repository runesleo/claude-code-workflow (711 stars, last pushed 4d ago), licensed MIT. It adds 227 tokens to every session, about $0.0011 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-30.
Other instructions, from other repositories
harness-workflow AGENTS.md
AGENTS.md instructions for YSAA1/harness-workflow, covering agents.md, 项目概览, 项目地图, 快速开始 and 项目铁律.
harness-workflow CLAUDE.md
Claude Code instructions for YSAA1/harness-workflow, a project described as: Context-aware agent workflow and project harness for Codex, Claude Code, and Cursor.
agentic-playwright selectors.instructions.md
Instructions for idavidov13/agentic-playwright, covering selector strategy, critical, instructions, phase 1: open and authenticate and phase 2: explore like a user.
awesome-copilot-id AGENTS.md
Instructions for GulajavaMinistudio/awesome-copilot-id, covering communication, explanation and documentation, markdown formatting, user communication style and workflow & methodology.
llm-ide-rules pytest-integration-tests.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering pytest integration tests and example integration test.
toki AGENTS.md
Instructions for choi138/toki, covering workspace rules, source of truth, toki workflow, required checks and global safety rules.