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-docnpx skills add MiaoDX/intuitive-flow --skill intuitive-docgit 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/intuitive-doc)<a href="https://agentmods.dev/skills/miaodx/intuitive-flow/intuitive-doc"><img src="https://agentmods.dev/badge/skills/miaodx/intuitive-flow/intuitive-doc.svg" alt="Measured on agentmods" 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 | $0.00064 | $0.00841 |
| Opus 5 | $0.00032 | $0.00420 |
| Sonnet 5 | $0.00013 | $0.00168 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
intuitive-doc 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 4d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intuitive Doc
Use this skill to keep the human-facing documentation surface small, current, and reviewable. The default human surface is:
README.md;ARCHITECTURE.md;STATUS.md;docs/human/**.
Planning logs, generated evidence, retrospectives, ADR detail, execution artifacts, scratch notes, and agent-only runbooks should stay outside the human surface unless a human doc intentionally promotes them.
Plan contracts use the fixed flat surface docs/plans/<slug>.md. Put lifecycle
in the plan's ## Plan Ledger and current execution state in
docs/status/active/, not in plan lifecycle directories or one-off prompt
files. Treat docs/plans/README.md, when present, as the plan dashboard rather
than a human-facing project manual.
This compact entrypoint preserves full mode-specific guidance in
references/detailed-guidance.md. Read it for detailed audit/update/cleanup
criteria, perspective levels, documentation standards, or full output format.
When To Activate
Use this skill when:
- root docs drift from current code, commands, or active plans;
- humans need a concise orientation after AI-heavy development;
- implementation changed public behavior, command surfaces, setup, architecture, or status;
- generated/planning/agent evidence has leaked into human docs;
- the user asks for documentation cleanup, human docs, README/architecture/status updates, or post-implementation doc alignment.
Modes
| Mode | Use when | Output | Redirect when |
|---|---|---|---|
| Audit | The user asks whether docs are current, bloated, or misplaced. | Findings, recommended changes, parked items, verification. | The issue is agent guidance, tests, or code layout. |
| Update | Current behavior, commands, architecture, or status changed. | Focused doc edits tied to current source evidence. | The requested change is only planning/evidence archival. |
| Cleanup | Human docs contain stale, duplicated, or over-detailed material. | Moved, archived, shortened, or removed docs with links preserved. | The material belongs in agent guidance or execution plans. |
| Guard | A proposed doc change needs placement review. | Placement decision and reason. | The user already selected the doc target and asks to edit. |
What ships with it
1 file 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.
- 4d ago First seen · 88 lines · 64 tokens per session scan A 1b51355904c9
intuitive-doc is a skill published in the GitHub repository MiaoDX/intuitive-flow (48 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 841 once invoked, about $0.0003 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.