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/asysta-act/agent-flow/claude-mdgit clone --depth 1 https://github.com/asysta-act/agent-flowWrote 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/asysta-act/agent-flow/claude-md)<a href="https://agentmods.dev/instructions/asysta-act/agent-flow/claude-md"><img src="https://agentmods.dev/badge/instructions/asysta-act/agent-flow/claude-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.05616 | $0.05616 |
| Opus 5 | $0.02808 | $0.02808 |
| Sonnet 5 | $0.01123 | $0.01123 |
| Haiku 4.5 | $0.00562 | $0.00562 |
Grade A, and why
agent-flow CLAUDE.md scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Operator trust required**: The `Webhook URL` value is dispatched via `curl` without scheme or host validation. Operators are responsible for configuring trusted URLs pointing to internal observability endpoints. SSRF d How it starts
The opening of the file, as written. The whole thing — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What This Is
A Claude Code plugin (agent-flow) that automates bug-fix workflows, feature implementation, and project scaffolding. It provides specialized agents that are orchestrated by commands to take an issue from triage through fix, review, test, and publish — or to scaffold a new project from scratch. The plugin is generic — all project-specific configuration lives in the consuming project's CLAUDE.md under ## Automation Config.
Author: Filip Sabacky
Installation: claude plugin marketplace add <path-to-repo>, then claude plugin install agent-flow@agent-flow
Repository Structure
No build system, no dependencies. Manual test suite in tests/. This is a pure plugin of markdown definitions.
.claude-plugin/— Plugin metadata (plugin.json,marketplace.json)agents/— 17 agent definitions (markdown with YAML frontmatter)skills/— 17 skills (slash commands)docs/guides/— Installation and configuration guidesdocs/reference/— Command, agent, pipeline, and config referenceexamples/— Config templates, custom agent examples, MCP config exampleschecklists/— Pipeline phase checklists (review, test, publish)tests/— Test harness with scenarios and CI workflow.agent-flow/— Per-run pipeline state files (state.json, pipeline.log, browser artifacts)state/— State schema documentationcore/— 17 shared pipeline pattern contracts
Architecture: 2-Layer System
Skills (orchestration — WHAT to do): /analyze-bug, /autopilot, /changelog, /check-setup, /create-backlog, /discuss, /fix-bugs, /implement-feature, /metrics, /onboard, /prioritize, /publish, /scaffold, /setup-agents, /setup-mcp, /sprint-plan, /version-check
Agents (specialists — HOW to do it): acceptance-gate, analyst, architect, backlog-creator, browser-agent, deployment-verifier, fixer, priority-engine, publisher, reviewer, rollback-agent, scaffolder, spec-analyst, spec-reviewer, spec-writer, sprint-planner, test-engineer
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.
- 3d ago First seen · 353 lines · 5,616 tokens per session scan A ec02a7e944f9
agent-flow CLAUDE.md is an instructions file published in the GitHub repository asysta-act/agent-flow (12 stars, last pushed 1mo ago), licensed MIT. It adds 5,616 tokens to every session, about $0.0281 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
hatch3r CLAUDE.md
Claude Code instructions for hatch3r/hatch3r, covering hatch3r — development instructions, architecture, development commands, two-axis pillar framework (2.0.0) and orchestrator self-discipline (bypass protection).
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
ken CLAUDE.md
Instructions for townsendmerino/ken, covering claude.md, what this is, repository ownership (read this first), commands and embedding parity & golden fixtures (now in aikit).
AI-System-Design-Consultant CLAUDE.md
Instructions for deepanshu2711/AI-System-Design-Consultant, covering claude.md, what this is, running it, load-bearing typos — do not "fix" these paths and agent node pattern.
cortex AGENTS.md
AGENTS.md instructions for tools-for-agents/cortex, covering agents.md — cortex, setup, the rules this repo is built on, tests and ci.