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/mlaurel/mcp-workflow-engine/claude-mdgit clone --depth 1 https://github.com/mlaurel/mcp-workflow-engineWhat 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.02156 | $0.02156 |
| Opus 5 | $0.01078 | $0.01078 |
| Sonnet 5 | $0.00431 | $0.00431 |
| Haiku 4.5 | $0.00216 | $0.00216 |
Grade A, and why
mcp-workflow-engine 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🤖 AGENTS.MD
AI Agent Instructions for agents-playbook repository
Repository Overview
This is a production-ready workflow automation repository for AI agents in software development. It provides YAML-based workflows, modular mini-prompts, and AI-powered semantic search to help AI agents perform development tasks efficiently.
Key Files & Structure
📋 Navigation & Discovery
playbook/prompt-playbook.md- MAIN NAVIGATOR - complete workflow guide and decision matrixREADME.md- Public documentation and MCP server setup guide- MCP Server - AI-powered workflow discovery
- Production: https://agents-playbook.vercel.app/api/mcp
- Local Dev: http://localhost:3000/api/mcp
🎯 Core Architecture
🔧 YAML Workflows (playbook/workflows/)
- feature-development.yml - Complete feature development lifecycle (14 steps)
- product-development.yml - Product from idea to launch (15 steps)
- quick-fix.yml - Bug fixes and hotfixes (4 steps)
- code-refactoring.yml - Code architecture improvements (8 steps)
- fix-tests.yml - Systematic test failure diagnosis and repair with refactoring integration (8 steps)
- fix-circular-dependencies.yml - Comprehensive circular dependency resolution with architectural refactoring (7 steps)
- unit-test-coverage.yml - Comprehensive unit test coverage improvement (7 steps)
- trd-creation.yml - Technical Requirements Document creation (7 steps)
- brd-creation.yml - Business Requirements with research (6 steps)
- brd-to-trd-translation.yml - Business to technical translation (6 steps)
- project-initialization.yml - New project setup (5 steps)
- infrastructure-setup.yml - Infrastructure deployment (12 steps)
🧱 Mini-Prompts Library (playbook/mini-prompts/)
Business Phase (business/)
gather-requirements.md- Requirements collection and analysisdocument-decisions.md- Decision documentation and rationale
Analysis Phase (analysis/)
feature-analysis.md- Feature scope and impact analysisarchitecture-analysis.md- System architecture evaluationcode-analysis.md- Code quality and structure analysistrace-bug-root-cause.md- Bug investigation and root cause analysis
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 · 236 lines · 2,156 tokens per session scan A c880493b76cb
mcp-workflow-engine CLAUDE.md is an instructions file published in the GitHub repository mlaurel/mcp-workflow-engine (0 stars, last pushed 1y ago), licensed MIT. It adds 2,156 tokens to every session, about $0.0108 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
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.
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.
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.