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/generator-draft-contract-parallelnpx skills add redker56/auto-harness --skill generator-draft-contract-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/generator-draft-contract-parallel)<a href="https://agentmods.dev/skills/redker56/auto-harness/generator-draft-contract-parallel"><img src="https://agentmods.dev/badge/skills/redker56/auto-harness/generator-draft-contract-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.00039 | $0.00490 |
| Opus 5 | $0.00019 | $0.00245 |
| Sonnet 5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
generator-draft-contract-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
Generator Draft Contract Parallel
This skill governs Generator contract mode.
At the start of this action, read these harness artifacts from the project:
.harness-parallel/status.md.harness-parallel/intake.md.harness-parallel/spec.md.harness-parallel/design-direction.md.harness-parallel/contracts/sprint-XX-contract.mdwhen revising the current sprint contract..harness-parallel/contracts/sprint-XX-review.mdwhen a prior review exists for the current sprint.
Then inspect the current project implementation relevant to this action:
- Read the current implementation, architecture, routes, components, services, tests, and config that define the current sprint boundary and feasibility.
- Use the codebase plus the harness artifacts to draft an implementation-ready contract.
Then read these skill references:
references/protocols/file-ownership.mdreferences/templates/sprint-contract.md
Follow these rules:
- Treat
.harness-parallel/intake.md,.harness-parallel/spec.md, the current sprint contract, and any current-sprint review artifact as authoritative inputs. - Write only the current sprint contract artifact.
- If a review file already exists for the sprint, revise the contract directly against it.
- Do not move the sprint toward implementation while the current sprint review result remains
REVISE. - Treat an approved review as implementation guidance and cautions, not just a pass/fail stamp.
- Keep the contract implementation-ready and evaluable from runtime plus named files.
- Include both a human-readable
Parallel Workstreamstable and a machine-readableDependency Graph JSONblock. - The JSON graph is the source of truth for worktree scheduling.
- Every node must declare non-overlapping
owned_paths, explicitdepends_on, and thebehavior_idsit owns. - If the sprint should stay serial, emit exactly one node and say why in notes instead of omitting the graph.
- Do not quietly violate locked architecture or stack choices; surface unavoidable deviations explicitly in the contract.
- Do not modify status, review, QA, retest, or final artifacts.
What ships with it
2 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.
- 5d ago First seen · 44 lines · 39 tokens per session scan A d35d840508a6
generator-draft-contract-parallel 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 490 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.