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 agentmods add skills/miaodx/intuitive-flow/intuitive-shapenpx skills add MiaoDX/intuitive-flow --skill intuitive-shapegit clone --depth 1 https://github.com/MiaoDX/intuitive-flowWhat 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 | $0.00126 | $0.00927 |
| Opus 5 | $0.00063 | $0.00464 |
| Sonnet 5 | $0.00025 | $0.00185 |
| Haiku 4.5 | $0.00013 | $0.00093 |
Grade A, and why
intuitive-shape 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 2d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intuitive Shape
Decide whether work deserves to exist before making it executable. Fixed appetite constrains the solution; it is not an estimate produced after scope is chosen.
Boundary
Own problem framing, appetite, rough solution elements, risk, explicit cuts, comparative bet selection, and the terminal decision. Do not implement, produce a task breakdown, create a backlog, or silently turn every idea into a project.
Route accepted work to the repository's canonical plan or preflight surface. Do not create a parallel source of truth when one already exists.
Stay out of tasks whose product decision is already settled. A small concrete fix, root-cause investigation, incident containment, or approved execution belongs to its normal diagnostic or execution route. Shape only when the user is deciding whether the work should exist, how much it deserves, which candidate wins, or what scope must be cut before commitment.
Shape The Decision
- Separate the observed problem from the suggested solution. Identify who has the problem, the costly status quo, and evidence that it matters now.
- Set an appetite before expanding the solution. Express the maximum justified time or effort and why spending more would be a bad bet.
- Sketch only the essential solution elements at rough fidelity. Preserve room for the builder to discover implementation details.
- Name rabbit holes, no-gos, and unresolved assumptions. Patch or cut risks that can consume the appetite.
- Define the smallest end-to-end core slice and an ordered cut list. A cut must reduce work while preserving the core outcome.
- When several candidates compete for capacity, compare them directly. Do not evaluate each in isolation and declare all of them worthy.
- Return exactly one decision:
BET: bounded, valuable, sufficiently understood, and worth doing now.RESEARCH: a cheap, time-boxed probe can resolve a decision-critical fact.RESHAPE: the problem matters, but the current solution does not fit the appetite.PASS: not worth capacity now; end without creating a permanent backlog item.
What ships with it
5 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.
- 2d ago First seen · 92 lines · 126 tokens per session scan A a4dc753ddb73
intuitive-shape is a skill published in the GitHub repository MiaoDX/intuitive-flow (48 stars, last pushed 7d ago), licensed MIT. It adds 126 tokens to every session and 927 once invoked, about $0.0006 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 skills, from other repositories
release
Create a new release with version bump, release notes, commit, and tag.
sub-tasks
View and manage SubFrame Sub-Tasks. Use when starting work, completing tasks, checking what's pending, or creating new tasks from conversation.
sub-audit
Run a code review and documentation audit on recent changes. Finds bugs, edge cases, missing docs, and type safety issues.
sub-docs
Sync all SubFrame documentation after feature work. Updates AGENTS.md lists, changelog, PROJECTNOTES decisions, and STRUCTURE.json.
sub-ipc
Regenerate the IPC channel reference documentation from ipcChannels.ts type maps.
onboard
Analyze project intelligence files and bootstrap SubFrame's STRUCTURE.json, PROJECTNOTES.md, and initial sub-tasks from existing codebase context.