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-testsgit 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-tests)<a href="https://agentmods.dev/skills/miaodx/intuitive-flow/intuitive-tests"><img src="https://agentmods.dev/badge/skills/miaodx/intuitive-flow/intuitive-tests/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-tests"><img src="https://agentmods.dev/badge/skills/miaodx/intuitive-flow/intuitive-tests.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.00396 |
| Opus 5.5 | $0.00012 | $0.00158 |
| Sonnet 5.5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
intuitive-tests 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.
What it actually says
Intuitive Tests
Improve test-suite signal and maintainability. Keep proof of observable behavior, real failure modes, and supported contracts; consolidate duplicates and remove assertions that merely restate implementation shape. Keep at least one meaningful proof of every behavior. Runtime discovery and packaging checks can be valuable contracts even when they look structural.
For broad or ambiguous cleanup, audit then propose a decision-complete slice. For a precise implementation request, execute that slice and park unrelated ideas. Keep existing repo test conventions; pytest examples are not a required taxonomy.
Modes
| Mode | Use when | Output | Redirect when |
|---|---|---|---|
| Audit / propose | Cleanup target is unclear | Evidence, candidates, bounded recommendation and proof plan | A slice is already approved |
| Prune / consolidate | Tests duplicate proof or bind internals | Smaller suite with behavior coverage preserved | No redundant proof exists |
| Marker / layout | Suite selection or paths need organization | Updated runners, consumers and collection proof | The issue is test value |
| Fixture / parameterize | Repeated setup or cases obscure intent | Shared setup or cases with readable diagnostics | Reuse is speculative |
Read value and pruning for test admission or deletion decisions; read suite structure only for markers, moves, fixtures, or parameterization. An audit may recommend a route without loading every implementation procedure.
Verify the changed behavior and affected runner/collection paths. Derive any external-service, hardware, or credential limits from current user/repo policy. Report kept/merged/deleted/reclassified tests, remaining proof, affected commands, and skipped checks with their actual reason.
What ships with it
4 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 4b94c82b1a66
- 26d ago Changed · +1 lines d8fc6830ba61
- 1mo ago Changed · -254 lines · -125 tokens per session aedaf23ff56d
- 1mo ago First seen · 290 lines · 154 tokens per session scan A d5cb06ccd376
intuitive-tests 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 396 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
dmvcframework-testing
Use when writing or fixing tests for a DelphiMVCFramework API — integration tests that drive real HTTP against an in-process server, or unit tests around controllers. Covers the DUnitX + in-process IMVCServer + IMVCRESTClient stack, CRUD/auth/authorization test patterns, database fixtures and the console runner.…
testing
Testing strategies and methodologies including TDD and E2E testing. Use when writing tests, implementing TDD workflow, or setting up E2E test infrastructure.
verify
Run the HUMHUM quality gates that are actually touched by the current diff — frontend typecheck + vitest, and Rust fmt/clippy/test — mirroring CI. Use before marking work done, opening a PR, or when asked to "verify", "check", or "run the gates".
parameterized-tests
Enforce native parameterized or table-driven tests when adding or modifying unit tests that exercise the same behavior with multiple data cases. Use whenever unit tests add repeated cases, edge-case matrices, or duplicated setup, execution, and assertions that differ only by case data.
better-testing
Review and improve how tests protect critical software behavior. Use when assessing missing unit, integration, contract, or end-to-end coverage; flaky tests; weak assertions; happy-path-only tests; excessive mocking; implementation-coupled tests; low-value snapshots; slow suites; or code that is difficult to test…
test-generation
Generate comprehensive tests for code including unit tests, integration tests, and edge case coverage. Analyzes code to identify testable units and generates tests matching the project's testing framework and conventions.