Flock is a desktop application for visually designing and running teams of AI agents, with a Rust backend and Tauri and React interface. It is used to orchestrate agent workflows that can perform tasks such as handling files, running commands, browsing the web, and executing pipelines, and the catalogue entries extend its agent and workflow setup.
Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skills/onelevenvy/flock/planning-with-files)<a href="https://agentmods.dev/skills/onelevenvy/flock/planning-with-files"><img src="https://agentmods.dev/badge/skills/onelevenvy/flock/planning-with-files/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/onelevenvy/flock/planning-with-files"><img src="https://agentmods.dev/badge/skills/onelevenvy/flock/planning-with-files.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.01903 |
| Opus 5 | $0.00028 | $0.00951 |
| Sonnet 5 | $0.00011 | $0.00381 |
| Haiku 4.5 | $0.00006 | $0.00190 |
Grade A, and why
planning-with-files 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 9d 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.
This is a copy
100% identical to planning-with-files — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning with Files
Work like Manus: Use persistent markdown files as your "working memory on disk."
FIRST: Check for Previous Session (v2.2.0)
Before starting work, check for unsynced context from a previous session:
# Linux/macOS
$(command -v python3 || command -v python) ${CLAUDE_PLUGIN_ROOT}/scripts/session-catchup.py "$(pwd)"
# Windows PowerShell
& (Get-Command python -ErrorAction SilentlyContinue).Source "$env:USERPROFILE\.claude\skills\planning-with-files\scripts\session-catchup.py" (Get-Location)
If catchup report shows unsynced context:
- Run
git diff --statto see actual code changes - Read current planning files
- Update planning files based on catchup + git diff
- Then proceed with task
Important: Where Files Go
- Templates are in
${CLAUDE_PLUGIN_ROOT}/templates/ - Your planning files go in your project directory
| Location | What Goes There |
|---|---|
Skill directory (${CLAUDE_PLUGIN_ROOT}/) |
Templates, scripts, reference docs |
| Your project directory | task_plan.md, findings.md, progress.md |
Quick Start
Before ANY complex task:
- Create
task_plan.md— Use templates/task_plan.md as reference - Create
findings.md— Use templates/findings.md as reference - Create
progress.md— Use templates/progress.md as reference - Re-read plan before decisions — Refreshes goals in attention window
- Update after each phase — Mark complete, log errors
Note: Planning files go in your project root, not the skill installation folder.
The Core Pattern
Context Window = RAM (volatile, limited)
Filesystem = Disk (persistent, unlimited)
→ Anything important gets written to disk.
File Purposes
| File | Purpose | When to Update |
|---|---|---|
task_plan.md |
Phases, progress, decisions | After each phase |
findings.md |
Research, discoveries | After ANY discovery |
progress.md |
Session log, test results | Throughout session |
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples.md 4.3 KB
- reference.md 7.9 KB
- scripts/check-complete.ps1 1.2 KB runs code
- scripts/check-complete.sh 1.1 KB runs code
- scripts/init-session.ps1 2.4 KB runs code
- scripts/init-session.sh 2.2 KB runs code
- scripts/session-catchup.py 7.3 KB runs code
- templates/findings.md 3.5 KB
- templates/progress.md 3.9 KB
- templates/task_plan.md 4.5 KB
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.
- 9d ago First seen · 249 lines · 56 tokens per session scan A 94e5791ae8b9
planning-with-files is a skill published in the GitHub repository Onelevenvy/flock (1,103 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,903 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to planning-with-files, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
code-review
This skill should be used when the user asks for a code review of a change — a pull request, merge request, branch, commit range, working-tree change, or pasted diff — covering correctness, security, performance, structure, and repository-specific rules. Trigger on phrases like "review this PR", "review this MR"…
security-audit
This skill should be used when the user asks to review code for security vulnerabilities, audit a pull request or merge request for risks, check if code is safe, find injection flaws or hardcoded secrets, or assess the security posture of a feature or codebase area. Use this skill even when the user doesn't say…
plan
This skill should be used when the user asks to explore a codebase and design implementation plans without making any changes. Trigger when users say 'plan how to implement X', 'design an approach for Y', 'explore the codebase before changing Z', 'create an implementation strategy', 'analyze how to refactor X', 'map…
init
This skill should be used when a user asks to initialize a repository for AI agents, create or update an AGENTS.md file, scaffold agent instructions for a codebase, or improve existing agent guidance. Triggers include phrases like 'create an AGENTS.md', 'set up agent instructions', 'initialize this repo for coding…
blog_creator
A writing aid for creating technical blog posts that explain software and other technical subjects in accessible language.
modern_poetry
A writing aid for creating modern poetry with imagery, metaphor, rhythm, and reflective ideas.