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/redker56/auto-harness/planner-spec-draft-parallelnpx skills add redker56/auto-harness --skill planner-spec-draft-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-spec-draft-parallel)<a href="https://agentmods.dev/skills/redker56/auto-harness/planner-spec-draft-parallel"><img src="https://agentmods.dev/badge/skills/redker56/auto-harness/planner-spec-draft-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 | $0.00049 | $0.00487 |
| Opus 5 | $0.00024 | $0.00244 |
| Sonnet 5 | $0.00010 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
planner-spec-draft-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 5d 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 Spec Draft Parallel
This skill governs Spec Draft Mode for the parallel Auto-Harness workflow.
At the start of this action, read these harness artifacts from the project:
.harness-parallel/intake.md.harness-parallel/status.md.harness-parallel/spec.mdwhen revising an existing spec..harness-parallel/design-direction.mdwhen revising an existing design direction.
Then inspect the current project implementation relevant to this action:
- Read the current implementation, architecture, routes, components, services, tests, and config that constrain or inform the spec and design direction.
- Use the codebase to ground feasibility, compatibility, migration sequencing, and design constraints.
Then read the same reference files used by skills/planner-spec-draft/, including its file-ownership protocol, spec template, design-direction template, and status-board template. Apply those rules to .harness-parallel/ paths.
Follow these rules:
- Update
.harness-parallel/intake.mdfirst so it stays the durable decision log. - Ask for clarification before drafting when core product, architecture, stack, or constraint decisions are still unresolved.
- Then write or revise
.harness-parallel/spec.mdand.harness-parallel/design-direction.md. - Keep
workflow_mode=parallelin.harness-parallel/status.md. - Use
pending_action=spec_approval_parallelwhen the spec is ready for user approval. - Do not read or write
.harness/. - Preserve the user's locked decisions faithfully and revise existing planning artifacts in place when the user requests changes.
- Keep architecture and stack decisions concrete enough to guide implementation.
- Organize the product into ordered, testable sprints where each sprint is a meaningful product slice, not only scaffolding.
- Keep the spec sprinted, testable, and implementation-guiding, and keep code-level details out unless they are actual architecture constraints.
- Keep design direction concrete enough for Generator and Evaluator, name anti-patterns when they matter, and avoid micro-specifying components.
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.
- 5d ago First seen · 38 lines · 49 tokens per session scan A 5d17289f8cdc
planner-spec-draft-parallel is a skill published in the GitHub repository redker56/auto-harness (14 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 487 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
하네스를 구성합니다. 전문 에이전트를 정의하며, 해당 에이전트가 사용할 스킬을 생성하는 메타 스킬. (1) '하네스 구성해줘', '하네스 구축해줘' 요청 시, (2) '하네스 설계', '하네스 엔지니어링' 요청 시, (3) 새로운 도메인/프로젝트에 대한 하네스 기반 자동화 체계를 구축할 때, (4) 하네스 구성을 재구성하거나 확장할 때, (5) '하네스 점검', '하네스 감사', '하네스 현황', '에이전트/스킬 동기화' 등 기존 하네스 운영/유지보수 요청 시 사용.
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.…
codex-code-review
Code review using Codex exec. Use when: PR review, code audit, second opinion on changes. Not for: doc review (use doc-review), security audit (use security-review). Output: severity-grouped findings + merge gate.