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 redker56/auto-harness --skill planner-clarifygit clone --depth 1 https://github.com/redker56/auto-harnessWrote 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/redker56/auto-harness/planner-clarify)<a href="https://agentmods.dev/skills/redker56/auto-harness/planner-clarify"><img src="https://agentmods.dev/badge/skills/redker56/auto-harness/planner-clarify.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.1 | $0.00039 | $0.00382 |
| Opus 5 | $0.00019 | $0.00191 |
| Sonnet 5 | $0.00008 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
planner-clarify 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 8d 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
Planner Clarify
This skill governs Clarification Mode for Auto-Harness.
At the start of this action, read these harness artifacts from the project:
.harness/intake.mdwhen it already exists..harness/status.mdwhen it already exists.
Then inspect the current project implementation only when the brief points to an existing project, codebase, or migration surface:
- Read the current app structure, entrypoints, routes, components, services, tests, and config that define the existing constraints or compatibility surface.
- Use the codebase to understand current reality and constraints; do not infer sprint scope, named defects, or implementation commitments from it.
Then read these skill references:
references/protocols/file-ownership.mdreferences/clarification/core.mdreferences/clarification/product.mdreferences/clarification/architecture.mdreferences/clarification/stack.mdreferences/clarification/constraints.mdreferences/catalogs/architecture-options.mdreferences/catalogs/consistency-patterns.mdreferences/catalogs/frontend-patterns.mdreferences/catalogs/stack-options.mdreferences/templates/intake-template.md
Follow these rules:
- Write only
.harness/intake.mdand.harness/status.md. - Produce a relay-ready numbered clarification questionnaire for the Orchestrator.
- Do not draft
.harness/spec.mdor.harness/design-direction.md. - If the user has not explicitly answered a clarification item, keep it unresolved rather than inferring it from the brief.
What ships with it
11 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.
- references/catalogs/architecture-options.md 1.0 KB
- references/catalogs/consistency-patterns.md 609 B
- references/catalogs/frontend-patterns.md 684 B
- references/catalogs/stack-options.md 871 B
- references/clarification/architecture.md 940 B
- references/clarification/constraints.md 580 B
- references/clarification/core.md 804 B
- references/clarification/product.md 625 B
- references/clarification/stack.md 769 B
- references/protocols/file-ownership.md 1.6 KB
- references/templates/intake-template.md 588 B
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.
- 8d ago First seen · 41 lines · 39 tokens per session scan A 9ebe3707123f
planner-clarify is a skill published in the GitHub repository redker56/auto-harness (14 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 382 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
harness-creator
Build, audit, and improve harnesses that make AI coding agents reliable: AGENTS.md/CLAUDE.md instruction files, feature/state tracking, verification gates, scope boundaries, session handoff, memory persistence, context budgets, tool-permission safety, and multi-agent coordination. Use this whenever a coding agent is…
harness
A meta-skill for designing and maintaining a project harness: a coordinated set of specialist agents, skills, and project instructions. It defines their roles, connects them to the project, and updates the setup as the work changes.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…