Borrowing it
Nothing to install: this file belongs to allcolor/PawFlow-Agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/allcolor/PawFlow-Agents/main/CLAUDE.mdgit clone --depth 1 https://github.com/allcolor/PawFlow-AgentsWrote 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/allcolor/pawflow-agents/claude-md)<a href="https://agentmods.dev/instructions/allcolor/pawflow-agents/claude-md"><img src="https://agentmods.dev/badge/instructions/allcolor/pawflow-agents/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.1 | $0.00737 | $0.00737 |
| Opus 5 | $0.00368 | $0.00368 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
PawFlow-Agents 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 7d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PawFlow — Development Context
What is PawFlow
PawFlow is a self-hosted AI agent orchestration platform inspired by Apache NiFi. It combines a data flow engine (FlowFile/Task/Service/Flow) with an LLM agent system that supports tool-use loops, multi-agent conversations, and streaming SSE.
Architecture
- Core: FlowFile (data unit), Task (processor), Service (connection), Flow (DAG)
- Engine: FlowExecutor (batch) + ContinuousFlowExecutor (queues/backpressure)
- Agents: AgentLoopTask with tool-use loop, multi-agent, streaming SSE
- Auth: AuthGatewayService with 9 OAuth providers
- Storage: ConversationStore (directory-based), MemoryStore, KnowledgeGraph, AgentDiary
- Relay: WebSocket reverse-tunnel for remote filesystem + tool execution
- CLI: PawCode (Claude Code drop-in replacement)
Key Conventions
- All documentation and code comments MUST be in English
- ALWAYS document new features, tools, tasks, services, and handlers — update the relevant file under
docs/in the same change - ALWAYS write unit tests for new code — handlers, tasks, services, parsers; nothing ships without coverage
- Zero backward compatibility — migration is one-shot, delete old code
- No "anonymous" or "default" fallbacks — missing required params = ValueError
- Every message MUST have UUID + timestamp at creation
- selectedAgent is NEVER empty in a conversation
- Force stop = immediate kill, NOT an error, NEVER affects the next loop
- All actions are async — nothing blocks UI or HTTP worker
- Bugs are always our code — never blame cache/OS/libs first
Expression Language
${scope.key:op1:op2("arg")} — 40+ chainable operations.
Resolution cascade: flow → conversation → user → global.
Tool Architecture
All filesystem tools extend BaseFsHandler and route through the relay service.
Tools execute in the relay Docker container by default, on the host if local=true.
No tool accesses the server filesystem directly (except internal storage: memories, KG, diary, graphs).
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.
- 7d ago First seen · 63 lines · 737 tokens per session scan A c5446b725cd0
PawFlow-Agents CLAUDE.md is an instructions file published in the GitHub repository allcolor/PawFlow-Agents (25 stars, last pushed yesterday), licensed MIT. It adds 737 tokens to every session, about $0.0037 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
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).
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.
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.