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/kesteva/soloflow/claude-mdgit clone --depth 1 https://github.com/kesteva/soloflowWrote 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/kesteva/soloflow/claude-md)<a href="https://agentmods.dev/instructions/kesteva/soloflow/claude-md"><img src="https://agentmods.dev/badge/instructions/kesteva/soloflow/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.01058 | $0.01058 |
| Opus 5 | $0.00529 | $0.00529 |
| Sonnet 5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
soloflow 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 4d 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 — 44 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.
Project Overview
SoloFlow is a hooks-based Claude Code workflow orchestration system that automates the product development lifecycle: idea extraction → refinement → execution → verification → learning. Distributed as a Claude Code plugin (git repo + thin plugin wrapper) installable per-project or globally.
See docs/ARCHITECTURE.md for the phase workflow, hook system, agent model strategy, and verification hierarchy.
This repo does not dogfood SoloFlow on itself. SoloFlow is the product built here, not the workflow used to build it. Do not run /soloflow:* commands, create .soloflow/ state, spawn SoloFlow agents, or otherwise invoke the SoloFlow pipeline to make changes to this codebase. Work on SoloFlow the way you'd work on any other repo: read files, make edits, run tests, commit. If a request seems to imply "use SoloFlow to improve SoloFlow," stop and ask — it's almost certainly not what the user meant.
Constraints every agent must know
Subagents cannot spawn subagents. Orchestration runs in the main session (/soloflow:sprint, /soloflow:compound, etc.); executors, verifiers, reviewers, and all other agent definitions are leaf nodes only.
Parallel task loops share a per-task worktree. When /soloflow:sprint or /soloflow:mad-max runs multiple non-conflicting tasks concurrently (governed by limits.max_parallel_tasks), the orchestrator creates a short-lived git worktree per task at .soloflow/worktrees/TASK-NNN/ and injects WORKTREE_ROOT: <abs path> into every subagent prompt for that task. Subagents must honor the directive (see each agent's "Working directory" section). Merge-back + settle-task.js run sequentially from the main worktree.
Context-limit handoffs. hooks/statusline.js writes context metrics to a bridge file; hooks/context-monitor.js (PostToolUse) reads it and injects WARNING (≤35% remaining) / CRITICAL (≤25%) into the agent conversation.
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.
- 4d ago First seen · 44 lines · 1,058 tokens per session scan A f65c77fe6c12
soloflow CLAUDE.md is an instructions file published in the GitHub repository kesteva/soloflow (40 stars, last pushed 3mo ago), licensed MIT. It adds 1,058 tokens to every session, about $0.0053 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).
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.