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 skills add MiaoDX/intuitive-flow --skill agent-planning-loopgit clone --depth 1 https://github.com/MiaoDX/intuitive-flowWrote 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/miaodx/intuitive-flow/agent-planning-loop)<a href="https://agentmods.dev/skills/miaodx/intuitive-flow/agent-planning-loop"><img src="https://agentmods.dev/badge/skills/miaodx/intuitive-flow/agent-planning-loop/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/miaodx/intuitive-flow/agent-planning-loop"><img src="https://agentmods.dev/badge/skills/miaodx/intuitive-flow/agent-planning-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 78 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00022 | $0.00746 |
| Opus 5.5 | $0.00009 | $0.00298 |
| Sonnet 5.5 | $0.00004 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
agent-planning-loop 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 22d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Planning Loop
Run a bounded planning debate when requested and return one judged recommendation. Implementation and approval happen after the loop, and questions for the user go through the main session, not the scouts. Preserve the full intended scope of a supplied plan unless the user selects a subset or a material decision blocks honest full-plan execution.
Plan artifact ownership
For a normal planning request, the canonical artifact is the target repository's
existing plan path. When the repository convention is docs/plans/, use one
docs/plans/<slug>.md file and reconcile the loop's accepted decisions into that
file. A planning loop reviews or updates the canonical plan; it does not create
.planning/, ROADMAP.md, STATE.md, phase CONTEXT.md, or a GSD PLAN.md as
a side effect.
Mentioning GSD, agents, or a planning loop does not itself authorize a GSD handoff. Stop at the canonical plan checkpoint for a planning-only request. A GSD artifact may be generated only when the user requests implementation/GSD handoff or an existing GSD phase already owns execution, and the named GSD workflow has actually been invoked.
Set a brief charter: goal, non-goals, context, permitted worker actions, and stop condition. Use scouts when preparing worker prompts and judging their evidence. Main-session judgment owns the recommendation.
Default to at most two rounds: discovery/challenge, then a narrowed follow-up only if it can change the recommendation. Stop sooner when a plan has clear acceptance and proof, the remaining items are implementation defaults, or a user decision blocks progress. A deeper autonomous loop requires the user's request.
Output
Return a review packet, not a transcript.
Include: planning loop status, what ran, rejected/parked items, one recommended
plan with scope/non-goals/acceptance/verification/risk, alternatives only when
material, user decisions, Plan artifact:, Recommended next action:, and
Shortcut:.
What ships with it
2 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.
- 22d ago Changed · +20 lines 815c923ce36b
- 26d ago Changed · +1 lines 00d7f572e4b7
- 1mo ago Changed · -140 lines · -114 tokens per session 2a44fe44adfd
- 1mo ago First seen · 191 lines · 136 tokens per session scan A 495b664811d0
agent-planning-loop is a skill published in the GitHub repository MiaoDX/intuitive-flow (48 stars, last pushed 8d ago), licensed MIT. It adds 22 tokens to every session and 746 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
spawn-agent
Spawn worker agents (Gemini CLI or Codex CLI) to keep main context clean. Use for implementation, codebase research, context gathering, or any scoped work that would pollute the orchestrator's context.
dev-updates
Detect and summarize uncommitted git changes grouped by feature area, then generate a structured commit message. Use when the user says "what's the update?", "what changed?", "summarize my changes", "what have I done?", or "what did I update?".
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
installing-cli-tools
Install, upgrade, configure, and verify developer CLI tools safely. Use when a user asks to install a new CLI, command-line app, SDK tool, package-manager binary, GitHub release binary, language runtime tool, or AI/vendor CLI; configure shell PATH/completions; run first login; set API keys, tokens, or env variables…
clipboard
Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".
neo4j-document-import-skill
Ingests unstructured and semi-structured documents into Neo4j as a knowledge graph. Use when chunking PDFs, HTML, plain text, or Markdown; extracting entities and relationships from text with an LLM (SimpleKGPipeline, neo4j-graphrag); loading JSON via apoc.load.json; building Document→Chunk→Entity graph structures; or…