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-fix-integratorgit 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-fix-integrator)<a href="https://agentmods.dev/skills/redker56/auto-harness/generator-fix-integrator"><img src="https://agentmods.dev/badge/skills/redker56/auto-harness/generator-fix-integrator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/redker56/auto-harness/generator-fix-integrator"><img src="https://agentmods.dev/badge/skills/redker56/auto-harness/generator-fix-integrator.svg" alt="Reviewed on agentmods" width="80" 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.00040 | $0.00565 |
| Opus 5 | $0.00020 | $0.00282 |
| Sonnet 5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
generator-fix-integrator 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 9d 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 Fix Integrator
This skill governs Generator fix integration 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.mdwhen the named defects touch UX, layout, or interaction rules..harness-parallel/contracts/sprint-XX-contract.md.harness-parallel/contracts/sprint-XX-review.mdwhen it exists for the current sprint..harness-parallel/runtime.md.harness-parallel/qa/sprint-XX-qa-report.md.harness-parallel/qa/sprint-XX-retest.mdwhen the current fix cycle follows a failed retest..harness-parallel/qa/sprint-XX-fix-log.mdwhen revising the current sprint fix log.
Then inspect the current project implementation relevant to this action:
- Read the source files, routes, components, services, tests, and config touched by the named defects and the necessary regression surface around them.
- Treat the main worktree as the integration surface and the worker branches named by the Orchestrator as merge inputs.
Then read these skill references:
references/protocols/file-ownership.mdreferences/templates/fix-log.mdreferences/templates/runtime-template.md
Follow these rules:
- Merge only the worker branches the Orchestrator names for the current pass.
- If not all temporary fix nodes are merged yet, perform merge work only and return structured merge results without writing
.harness-parallel/qa/sprint-XX-fix-log.mdor updating runtime notes. - Once all fix-workstream nodes are merged, finish any tightly related cleanup still required for the named defects.
- Fix only defects named in the current QA or retest context unless a tightly related adjustment is required.
- Treat the current sprint review, when present, as implementation guidance and cautions that still apply during the fix cycle.
- Treat the Orchestrator's named bug batches plus
## Parallel Execution Stateas the source of truth for merge ordering. - Update the runtime contract when startup, access, or healthcheck behavior changed.
- Record the actual fixes in the sprint fix log.
- Keep the fix log tied to named defects, changed files, and any verification notes that matter for retest.
- Do not rewrite QA or retest artifacts yourself.
What ships with it
3 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.
- 9d ago First seen · 47 lines · 40 tokens per session scan A f472b4b9e147
generator-fix-integrator is a skill published in the GitHub repository redker56/auto-harness (14 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 565 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
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.
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…
generate-runner
Generate a customized precommit runner for any ecosystem. Use when: non-Node projects need a runner, eject from generic runner, customize runner for project. Not for: running precommit (use /precommit), installing runner (handled by auto-install). Output: customized runner script with eject header.
jira
Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).
precommit
Pre-commit checks — lint:fix -> build -> test.