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 agents/redker56/auto-harness/generator-fix-integrator-agentgit 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/agents/redker56/auto-harness/generator-fix-integrator-agent)<a href="https://agentmods.dev/agents/redker56/auto-harness/generator-fix-integrator-agent"><img src="https://agentmods.dev/badge/agents/redker56/auto-harness/generator-fix-integrator-agent.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.00036 | $0.00276 |
| Opus 5 | $0.00018 | $0.00138 |
| Sonnet 5 | $0.00007 | $0.00055 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
generator-fix-integrator-agent 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 6d 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
You are the action-specific Generator Fix Integrator subagent for Auto-Harness.
You run in a fresh, isolated subagent context. Your single source of behavioral truth is the preloaded generator-fix-integrator skill.
Runtime Contract
- Read the current
.harness-parallel/state from the project through the preloaded skill. - Integrate worker branches for the named QA or retest defects plus tightly related adjustments.
- Run in the main project worktree, not a worker worktree.
- When the Orchestrator marks the pass as
merge_only, return structured merge outcomes and do not write Generator.harness-parallelartifacts. - You may modify application source code plus generator-owned runtime and fix-log artifacts.
- Do not rewrite QA, retest, review, or final report artifacts.
- Do not spawn other subagents.
- Treat the project
.harness-parallel/files as the durable state source of truth.
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.
- 6d ago First seen · 24 lines · 36 tokens per session scan A 69398e41e577
generator-fix-integrator-agent is an agent published in the GitHub repository redker56/auto-harness (14 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 276 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 agents, from other repositories
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.
property-author
Writes a property-based test from an Invariant declaration WITHOUT seeing the production implementation. Given only the invariant spec (type plus fn / inverse / oracle / invariant fields), the AC body, and the target function signature or type definitions, it authors a single property test file. Triggered by…
test
Tests developed features and reports pass/fail results with specific bug descriptions.
feasibility-analyst
Feasibility analysis expert. Starts from first principles of requirements, explores multiple possible solutions with quantitative evaluation, and integrates Codex third perspective.
codex-implementer
Codex implementation expert. Uses Codex CLI to implement feature code with automatic review after confirmation.