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 generator-build-workergit 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-build-worker)<a href="https://agentmods.dev/skills/redker56/auto-harness/generator-build-worker"><img src="https://agentmods.dev/badge/skills/redker56/auto-harness/generator-build-worker.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.00023 | $0.00307 |
| Opus 5 | $0.00012 | $0.00153 |
| Sonnet 5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
generator-build-worker 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
Generator Build Worker
This skill governs a worktree-bound Generator build worker.
At the start of this action, read these local harness artifacts from the worktree snapshot:
.harness-parallel/status.md.harness-parallel/intake.md.harness-parallel/spec.md.harness-parallel/design-direction.md.harness-parallel/contracts/sprint-XX-contract.md.harness-parallel/contracts/sprint-XX-review.mdwhen it exists for the current sprint
Then inspect the current project implementation relevant to this action:
- Read the assigned owned files or globs first.
- Read neighboring files only as dependency context unless the Orchestrator explicitly assigned them to you.
- Treat this worktree as isolated. Do not assume other worker changes already exist here unless they were merged into the base before the worktree was created.
Follow these rules:
- Implement only the assigned dependency-graph node.
- Modify only the owned files or globs named by the Orchestrator.
- Do not modify
.harness-parallel/files. - Run targeted verification for your node before finishing.
- Make a local git commit in this worktree.
- If your task cannot be completed without touching an unowned path, stop short of freelancing and report the blocker clearly.
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 · 34 lines · 23 tokens per session scan A 4f1e46daa19d
generator-build-worker is a skill published in the GitHub repository redker56/auto-harness (14 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 307 once invoked, about $0.0001 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…