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/fayzan123/claude-workflow-composer/agents-mdgit clone --depth 1 https://github.com/fayzan123/claude-workflow-composerWrote 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/fayzan123/claude-workflow-composer/agents-md)<a href="https://agentmods.dev/instructions/fayzan123/claude-workflow-composer/agents-md"><img src="https://agentmods.dev/badge/instructions/fayzan123/claude-workflow-composer/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.1 | $0.04819 | $0.04819 |
| Opus 5 | $0.02410 | $0.02410 |
| Sonnet 5 | $0.00964 | $0.00964 |
| Haiku 4.5 | $0.00482 | $0.00482 |
Grade A, and why
claude-workflow-composer 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 6d 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file gives durable repository guidance to Codex and other coding agents. Keep it accurate, compact, and focused on conventions that should apply across tasks. Put narrower overrides in a nested AGENTS.md or AGENTS.override.md near the code they govern.
Project Identity
Claude Workflow Composer (CWC) is a local-first, full-stack TypeScript app for finding repeated Claude Code work and compiling it into the smallest fitting artifact: an owned guidance rule, plain skill, managed loop, or multi-agent workflow. It has:
- An Express server under
src/server/. - A React 19 + React Flow client under
client/src/. - Pure core TypeScript modules under
src/. - An npx-runnable CLI entry under
bin/. - Local storage under
~/.cwc/and exported Claude assets under~/.claude/or project-local.claude/.
The trust model is local and filesystem-based. Be conservative around auth, CORS, filesystem writes, guidance-file edits, shell execution, exported skills/agents, and automation runs.
Current Product Roadmap
The approved roadmap is maintained in:
docs/specs/2026-07-14-cwc-product-roadmap-design.mddocs/plans/2026-07-14-cwc-product-roadmap-plan.mddocs/specs/2026-07-16-right-sized-generation-design.md
Read all three before starting roadmap work. Stage 1 and right-sized generation are implemented: managed runs have server-owned manifests and safe Apply/Discard, while detection now classifies and produces rules, skills, loops, or workflows. Proceed next in this order:
- Deployment registry across user and project exports.
- Canonical
.cwcparsing, migrations, import, duplicate, and portable sharing. - Codex as an additional history source without changing Claude Code export/runtime.
- Optional Codex analysis/planning backend, independently selectable from history source.
- ChatGPT ingestion only from an explicit local data export.
Keep history source, analysis backend, deployment target, artifact tier, and workflow runtime as independent concepts. Through the approved roadmap, Claude Code remains the deployment target and managed-run runtime. Do not jump ahead to provider abstraction before deployment tracking and canonical parsing are complete.
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.
- 6d ago First seen · 280 lines · 4,819 tokens per session scan A 39d0322b0ce8
claude-workflow-composer AGENTS.md is an instructions file published in the GitHub repository fayzan123/claude-workflow-composer (35 stars, last pushed 1mo ago), licensed MIT. It adds 4,819 tokens to every session, about $0.0241 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
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).
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 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).
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.