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 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/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/intuitive-doc"><img src="https://agentmods.dev/badge/skills/miaodx/intuitive-flow/intuitive-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00777 |
| Opus 5.5 | $0.00012 | $0.00311 |
| Sonnet 5.5 | $0.00006 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00078 |
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 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 — 87 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.
For plan and task-state placement, follow plan selection. Preserve the repo's existing canonical plans and lifecycle layout. When adopting Intuitive defaults, use a flat plan directory and keep current execution state in the task-owned resume surface. A plan dashboard is an agent navigation aid.
This compact entrypoint preserves full mode-specific guidance in detailed guidance. 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
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 · -2 lines 92f22111f96a
- 26d ago Changed · +1 lines ecc052a1fa01
- 27d ago Changed · -1 lines 561f81cd9a59
- 1mo ago Changed · +1 lines · -35 tokens per session 588c79c00d8e
- 1mo 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 8d ago), licensed MIT. It adds 29 tokens to every session and 777 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…