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-clarify-parallelgit 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-parallel)<a href="https://agentmods.dev/skills/redker56/auto-harness/planner-clarify-parallel"><img src="https://agentmods.dev/badge/skills/redker56/auto-harness/planner-clarify-parallel.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.00046 | $0.00374 |
| Opus 5 | $0.00023 | $0.00187 |
| Sonnet 5 | $0.00009 | $0.00075 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
planner-clarify-parallel 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 7d 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 Parallel
This skill governs Clarification Mode for the parallel Auto-Harness workflow.
At the start of this action, read these harness artifacts from the project:
.harness-parallel/intake.mdwhen it already exists..harness-parallel/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 the same reference files used by skills/planner-clarify/, including its clarification guides, catalogs, file-ownership protocol, and intake template. Apply those rules to .harness-parallel/ paths.
Follow these rules:
- Write only
.harness-parallel/intake.mdand.harness-parallel/status.md. - Set
workflow_mode=parallelandpending_action=brief_clarification_parallelin.harness-parallel/status.md. - Produce a relay-ready numbered clarification questionnaire for the Orchestrator.
- Do not draft
.harness-parallel/spec.mdor.harness-parallel/design-direction.md. - Do not read or write
.harness/. - If the user has not explicitly answered a clarification item, keep it unresolved rather than inferring it from the brief.
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.
- 7d ago First seen · 31 lines · 46 tokens per session scan A 7a46b7266e9f
planner-clarify-parallel is a skill published in the GitHub repository redker56/auto-harness (14 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 374 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).
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.…
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.
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…