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-squashgit 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-squash)<a href="https://agentmods.dev/skills/miaodx/intuitive-flow/intuitive-squash"><img src="https://agentmods.dev/badge/skills/miaodx/intuitive-flow/intuitive-squash/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-squash"><img src="https://agentmods.dev/badge/skills/miaodx/intuitive-flow/intuitive-squash.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Tool Misuse · line 188 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00032 | $0.00385 |
| Opus 5.5 | $0.00013 | $0.00154 |
| Sonnet 5.5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
intuitive-squash 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 20d 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.
What it actually says
Intuitive Squash
Turn noisy local history into reviewable commits without changing the final tree. Read planning to resolve the base, run the bundled read-only preflight, identify preserved commits, and propose the commit map. Do not mutate branches or the worktree during planning.
Modes
Offer both modes by default, unless the user requests one exact strategy:
| Mode | Commit shape |
|---|---|
| Aggressive | The fewest coherent reviewable commits, while keeping preserved commits and unrelated change surfaces separate. |
| Moderate | Semantic review and rollback boundaries with phase and fixup churn removed; prefer this for large or high-risk branches. |
State the recommended mode and why, then use the mode the user approves for the commit map. For a small stack, the plans may differ only slightly; do not invent splits to make them look different.
Keep marked, security/hotfix, configured-path, and other-author commits standalone as the preflight requires. Disclose publication, merge, signature, and tag risks; record the original-to-final mapping, planned HEAD, backup, and stash strategy. Never rewrite until the user approves the exact plan and applicable risk gates.
Once approved, read rewrite and restore. Recheck planned state, back up before rewriting, verify final tree equality and preserved commit mappings, then restore dirty work. Keep the backup; retain the stash on verification failure or restoration conflict. Report proof and recovery state. Push only when separately authorized, with an explicit expected-old-OID lease if rewriting published history.
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.
- 20d ago Changed · +13 lines · +8 tokens per session ab4023d57fea
- 1mo ago Changed · -165 lines · -49 tokens per session c08a5e070155
- 1mo ago First seen · 190 lines · 73 tokens per session scan A ac7ffed1d9bf
intuitive-squash is a skill published in the GitHub repository MiaoDX/intuitive-flow (48 stars, last pushed 8d ago), licensed MIT. It adds 32 tokens to every session and 385 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
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?".
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
commit
Generate a conventional commit message for staged changes.
ox-cli-pr-header
Emit and paste the SageOx credit line at the TOP of a pull-request description — the human-facing counterpart to the machine SageOx-Session: trailer. Run ox pr header at PR-creation time; it renders a thin, on-brand, dark/light-aware single line linking the session(s), plan(s), and discussion(s) that produced the…
chinese-commit-conventions
A Chinese-language convention for writing Git commit messages, based on Conventional Commits, a standard format that tools can use to classify changes and build changelogs.
commit
Create a well-formatted conventional commit with proper message structure. Use when ready to commit changes.