Break a large task into a concrete, ordered implementation plan before writing code. Use for multi-file features, refactors, or anything non-trivial where a plan prevents rework.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Plan
Before non-trivial implementation, produce a plan the user can sanity-check. This catches bad assumptions early and reduces rework.
## When to use
- Multi-file features or refactors.
- Anything with >3 steps or unclear scope.
- When the user says "plan this out" / "how would you approach …".
## Procedure
1. **Understand the goal.** Restate it in one sentence. If ambiguous, ask a focused question (use the `clarify` tool) before planning.
2. **Survey the relevant code.** Read the files/areas that will change. Ground the plan in real symbols and paths, not guesses.
3. **Produce a sequenced plan:**
- Ordered steps, each with: what changes, which files, and the verification for that step.
- Flag decisions/risks and unknowns explicitly.
- Note what is deliberately out of scope.
4. **Propose the plan for sign-off** before implementing. Don't start editing until the user agrees (unless the task was explicitly "just do it").
5. **Track progress** with the `todo` tool as you implement; update statuses as steps complete.
## Good plan properties
- **Concrete:** names files and functions, not "update the auth module".
- **Ordered:** step N doesn't depend on step N+2.
…
The line at the top of this page pins the label git:20260624.52cbbd6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (1774 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
metaspartan/cybara · 32 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ontfxhpnhxgzn6bt
GET https://markdownregistry.com/api/v1/resolve?ref=metaspartan/cybara/plan
GET https://markdownregistry.com/api/v1/blob/99c8706b99fbfe4c155b475727c44994a1e20f22224abcd17539ef1dc752cc09
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
metaspartan/cybara · plugins/blender-workflows/skills/blender-headless/SKILL.md · Build, render, and visually verify 3D models with Blender's Python API in headless mode, using the image tool to…
metaspartan/cybara · plugins/browser-quality/skills/browser-qa/SKILL.md · Validate web applications through the embedded browser with responsive, interaction, console, and screenshot checks.
metaspartan/cybara · plugins/data-workflows/skills/database-operations/SKILL.md · Inspect schemas, debug queries, plan migrations, and validate data changes across common relational databases.
metaspartan/cybara · plugins/game-development/skills/bevy/SKILL.md · Build, test, debug, and optimize Rust games and tools using the Bevy engine, ECS scheduling, assets, rendering, and…
metaspartan/cybara · plugins/game-development/skills/game-development/SKILL.md · Route and execute game project work across Unreal Engine, Unity, Godot, Bevy, browser engines, assets, performance…
metaspartan/cybara · plugins/game-development/skills/game-networking/SKILL.md · Design, implement, test, secure, and profile multiplayer game networking across engines, including authority…
metaspartan/cybara · plugins/game-development/skills/game-playtesting/SKILL.md · Test a game end to end like a player across boot, controls, gameplay loops, UI, save state, failure recovery…
jeremylongshore/tons-of-skills-marketplace · plugins/ai-agency/hyperflow/skills/plan/SKILL.md · Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to…
zereight/gitlab-mcp · .github/skills/plan/SKILL.md · Strategic planning with optional interview workflow. Activate when user says: plan this, plan the, let's plan, make a…
suboss87/fdeops · skills/plan/SKILL.md · Sequence an understood outcome into verifiable delivery slices with dependencies, ownership and acceptance checks. Use…
snowflake-labs/cocoplus · .cortex/skills/cocobrew/plan/SKILL.md · Enter the Plan phase of CocoBrew. Runs CocoSpec quality gate pre-flight, reads spec.md and discuss.md (if present)…
boshu2/agentops · skills/plan/SKILL.md · Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Use…
boshu2/agentops · plugin/skills/plan/SKILL.md · Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Use…
