Vibe-Skills is a collection and routing system that helps AI agents discover, select, and coordinate specialized skills for completing tasks. It is intended for agents that need to organize workflows across many installed capabilities. The catalogue entries are skills and an agent belonging to this system.
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/foryourhealth111-pixel/vibe-skills/planning-with-files)<a href="https://agentmods.dev/skills/foryourhealth111-pixel/vibe-skills/planning-with-files"><img src="https://agentmods.dev/badge/skills/foryourhealth111-pixel/vibe-skills/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/foryourhealth111-pixel/vibe-skills/planning-with-files"><img src="https://agentmods.dev/badge/skills/foryourhealth111-pixel/vibe-skills/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.00047 | $0.01559 |
| Opus 5 | $0.00023 | $0.00779 |
| Sonnet 5 | $0.00009 | $0.00312 |
| Haiku 4.5 | $0.00005 | $0.00156 |
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.
Copies of this mod
4 near-identical copies found in the catalogue:
- planning-with-files — 98% identical, 2 lines differ
- planning-with-files — 98% identical, 2 lines differ
- planning-with-files — 97% identical, 43 lines differ
- planning-with-files — 97% identical, 43 lines differ
How it starts
The opening of the file, as written. The whole thing — 212 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."
Important: Where Files Go
When using this skill:
- Templates are stored in the skill directory at
${CLAUDE_PLUGIN_ROOT}/templates/ - Your planning files (
task_plan.md,findings.md,progress.md) should be created in your project directory — the folder where you're working
| Location | What Goes There |
|---|---|
Skill directory (${CLAUDE_PLUGIN_ROOT}/) |
Templates, scripts, reference docs |
| Your project directory | task_plan.md, findings.md, progress.md |
This ensures your planning files live alongside your code, not buried in the skill installation folder.
Quick Start
Before ANY complex task:
- Create
task_plan.mdin your project — Use templates/task_plan.md as reference - Create
findings.mdin your project — Use templates/findings.md as reference - Create
progress.mdin your project — 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: All three planning files should be created in your current working directory (your project root), not in the skill's 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 |
Critical Rules
1. Create Plan First
Never start a complex task without task_plan.md. Non-negotiable.
2. The 2-Action Rule
"After every 2 view/browser/search operations, IMMEDIATELY save key findings to text files."
What ships with it
7 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.
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 · 212 lines · 47 tokens per session scan A 67a8557a5bc8
planning-with-files is a skill published in the GitHub repository foryourhealth111-pixel/Vibe-Skills (3,252 stars, last pushed 12d ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,559 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
cli-framework-cli-commander
Node.js CLI development with Commander.js and @clack/prompts - command structure, interactive prompts, wizard state machines, config hierarchies, exit codes, cancellation handling.
cli-prompts-clack
Beautiful interactive CLI prompts with @clack/prompts and custom prompts with @clack/core.
cli-framework-oclif-ink
Modern CLI development combining oclif's command framework with Ink's React-based terminal rendering.
founder-coach
Personal leadership development for founders and first-time CEOs. Use when a founder feels like the bottleneck, struggles to delegate, is burning out, or transitioning from IC to executive.
knowledge-ops
Audit and repair an internal knowledge base — staleness, ownership gaps, orphans, duplication, and findability. Use when the wiki is untrusted, docs are out of date, nobody owns pages, or search returns the wrong answer.
escalation-policy
Use when a ticket must be handed to a human agent instead of resolved by the AI.