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/wangbinquan/agent-workflow/agents-mdgit clone --depth 1 https://github.com/wangbinquan/agent-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.00263 | $0.00263 |
| Opus 5 | $0.00131 | $0.00131 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
agent-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 agent instructions
- Before starting work, read
CLAUDE.mdandSTATE.md, then follow the current repository guidance in those files.
Commit attribution
- When an AI coding agent materially contributes to a commit, append a standard Git co-author trailer using the actual agent or model name and its provider's noreply email:
Co-Authored-By: <agent-or-model-name> <provider-noreply-email> - For Claude Fable 5, use exactly:
Co-Authored-By: Claude Fable 5 <[email protected]> - Replace every placeholder with the contributing session's real values. Do not hard-code one vendor, product, model, or email for all agents, and do not attribute a commit to an agent that did not materially contribute.
- If multiple agents materially contributed to one commit, add one non-duplicated
Co-Authored-Bytrailer per contributing agent. - Do not add an agent co-author trailer to a human-only commit.
- After committing and before pushing, verify the trailer with
git show -s --format=%B HEAD. If a required trailer is missing, fix it before push; do not rewrite already-pushed shared history solely to add or change attribution.
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 · 15 lines · 263 tokens per session scan A c30cebe7866b
agent-workflow AGENTS.md is an instructions file published in the GitHub repository wangbinquan/agent-workflow (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 263 tokens to every session, about $0.0013 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
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.
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).
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.