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/skill-runnernpx skills add MiaoDX/intuitive-flow --skill skill-runnergit 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/skill-runner)<a href="https://agentmods.dev/skills/miaodx/intuitive-flow/skill-runner"><img src="https://agentmods.dev/badge/skills/miaodx/intuitive-flow/skill-runner.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.00045 | $0.00998 |
| Opus 5 | $0.00023 | $0.00499 |
| Sonnet 5 | $0.00009 | $0.00200 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
skill-runner 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 3d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Runner
Use skill-runner when an isolated worker needs durable logs, compact result
artifacts, explicit path ownership, or supervision across a long task. Small
read-only probes and tiny edits should stay on the host-approved lighter route.
Read references/codex-delegation.md before choosing a Codex worker surface.
That file is the canonical policy for Paseo probing, native subagent
disablement, and tmux fallback.
Launch Contract
Before launch, define:
- objective and named skills;
- owned paths and non-goals;
- the smallest context package;
- task-specific acceptance and verification;
- stop conditions and final
RESULT_STATUScontract; - review cadence for long-running work.
Use the runner's own help as the option source of truth:
uv run python skills/skill-runner/scripts/run_skill_runner.py --help
Codex prompt workers inherit the current Codex provider configuration and auth
by default. This keeps ordinary supervised runs on the same working route as
the parent session. Provider bakeoffs must pass --codex-config-mode isolated;
that mode ignores user config and uses the explicit provider, base URL, env-key,
and wire-API arguments supplied by the bakeoff runtime.
Launch from the target repo and pass the worker prompt after --. Use
--dry-run first when validating a new agent, model, launch mode, or ownership
split. Use --dangerous only with explicit authorization. Do not infer missing
acceptance criteria or credentials just to make a worker start.
The script writes runs under ~/.cache/skill-runner/runs/ by default. Inspect
compact artifacts before full logs:
result.md: normalized task result and blocker reason;eval.md: scope, diff, proof, and ownership review;skill-review.md: reusable skill feedback, advisory only;run.json: selected agent, workspace, owned paths, and sandbox posture;terminal.log: debugging evidence when compact artifacts disagree.
For batch review, use the summarizer's help rather than duplicating its options here:
What ships with it
3 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.
- 3d ago First seen · 115 lines · 45 tokens per session scan A 79e0fcec7740
skill-runner is a skill published in the GitHub repository MiaoDX/intuitive-flow (48 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 998 once invoked, about $0.0002 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.