propose-harness-change

propose-harness-change is a skill for Claude Code, Codex from Rockielab/rockie-codex. It costs 134 tokens per session (1,100 once invoked), scanned A, a copy of propose-harness-change, Apache-2.0.

A controlled workflow for proposing changes to an agent harness, such as a new hook, script fix, or improved skill. Separate Generator, Verifier, and Updater roles create, audit, and prepare the patch.

In plain words
What is it for?
Use it to prepare a reviewed patch for the Rockie harness, including its rationale and a targeted smoke test.
Why use it?
It adds independent review and tests before a self-improvement change is accepted, reducing the risk of unverified harness changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

Good fit Use it to prepare a reviewed patch for the Rockie harness, including its rationale and a targeted smoke test.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rockielab/rockie-codex/propose-harness-change
Install

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.

Any agent
npx skills add Rockielab/rockie-codex --skill propose-harness-change
Clone the repo
git clone --depth 1 https://github.com/Rockielab/rockie-codex

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for propose-harness-change

README.md
[![agentmods](https://agentmods.dev/badge/skills/rockielab/rockie-codex/propose-harness-change/github.svg)](https://agentmods.dev/skills/rockielab/rockie-codex/propose-harness-change)
Your own site
<a href="https://agentmods.dev/skills/rockielab/rockie-codex/propose-harness-change"><img src="https://agentmods.dev/badge/skills/rockielab/rockie-codex/propose-harness-change/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.

agentmods 80×15 button for propose-harness-change

Your own site · 80×15
<a href="https://agentmods.dev/skills/rockielab/rockie-codex/propose-harness-change"><img src="https://agentmods.dev/badge/skills/rockielab/rockie-codex/propose-harness-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 134 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,100 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 92% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00134 $0.01100
Opus 5 $0.00067 $0.00550
Sonnet 5 $0.00027 $0.00220
Haiku 4.5 $0.00013 $0.00110

Measured 10d ago against content hash 124c0809ee38, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

propose-harness-change 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 10d 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.

Origin

This is a copy

92% identical to propose-harness-change — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

project-extension/agents/skills/propose-harness-change/SKILL.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/propose-harness-change — safe self-improvement

Autonomous research harnesses that let the agent edit themselves tend to drift (MINJA / eTAMP memory-poisoning, arXiv 2603.29231's finding that "memory scaffolds universally decrease long-horizon reliability", the Ouroboros "AGENTS.md rewrite" footgun). rockie's discipline is Generator / Verifier / Updater separation — nobody is allowed to propose, verify, and commit in the same role.

The three roles

Generator (the proposing agent)

  • Writes the diff against a LOCAL CLONE of the rockie source repo.
  • Writes a short rationale: what pattern broke, why the fix composes with existing differentiators, what smoke-test assertion(s) prove it.
  • Never commits directly. Produces a patch file ~/rockie-proposals/<YYYY-MM-DD-slug>/patch.diff plus rationale.md, test.sh (the specific smoke-test snippet).

Verifier (fresh-context audit agent)

  • Dispatched via the Agent tool with NO prior context.
  • Reads the patch + rationale, the files being touched, and the CONTRIBUTING.md composition rules.
  • Must answer four questions with evidence:
    1. Does this compose with the existing differentiators, or duplicate one of them?
    2. Does the smoke test actually test the claimed improvement?
    3. Is the change local (one file) or does it ripple across the schema?
    4. Is there a path-traversal, SQL-injection, or shell-injection regression?
  • Returns APPROVE | CHANGES_REQUESTED | REJECT with a short report.

Updater (the human)

  • Reviews Verifier report + diff.
  • Runs bash tests/smoke-test.sh in the rockie clone — must be green.
  • If everything looks right, runs scripts/apply_upstream_patch.sh <proposal-dir> which commits the diff locally with the rationale as the commit message, then offers gh pr create.
  • The human — not the agent — chooses when to push.

Invocation

Normal flow (agent finds a harness-level improvement during work):

[LEARN harness-upstream] apply_patch.py should normalize Windows line endings before SEARCH match

Read the full file on GitHub · 99 lines

Changes

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.

  1. 10d ago First seen · 99 lines · 134 tokens per session scan A 124c0809ee38

Subscribe to this mod's changes

propose-harness-change is a skill published in the GitHub repository Rockielab/rockie-codex (20 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 134 tokens to every session and 1,100 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to propose-harness-change, differing in 4 lines, and is treated as a copy.