upstream-contribute

upstream-contribute is a skill for Claude Code from Rockielab/rockie-codex. It costs 169 tokens per session (3,135 once invoked), scanned A, original, Apache-2.0.

A skill for finding reusable improvements in the current Codex session and preparing them for contribution to the public rockie-codex project. It removes project-specific details before sending the idea for review.

In plain words
What is it for?
It is for identifying general improvements to hooks, skills, memory structures, and harness behavior, then preparing a reviewable upstream contribution.
Why use it?
It helps share broadly useful fixes and patterns without publishing details that only apply to one project.

Skill for Claude Code

Written for Claude Code: PreCompact hook event. Also seen: mentions subagents; mentions Claude Code; mentions Codex.

Good fit It is for identifying general improvements to hooks, skills, memory structures, and harness behavior, then preparing a reviewable upstream contribution.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rockielab/rockie-codex/upstream-contribute
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 upstream-contribute
Clone the repo
git clone --depth 1 https://github.com/Rockielab/rockie-codex

Made for: Claude Code.

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 upstream-contribute

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/rockielab/rockie-codex/upstream-contribute"><img src="https://agentmods.dev/badge/skills/rockielab/rockie-codex/upstream-contribute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 169 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,135 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 original No closer match found 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.00169 $0.03135
Opus 5 $0.00084 $0.01568
Sonnet 5 $0.00034 $0.00627
Haiku 4.5 $0.00017 $0.00314

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

Security

Grade A, and why

upstream-contribute 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.

project-extension/agents/skills/upstream-contribute/SKILL.md · 295 lines

How it starts

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

$upstream-contribute — meta-loop: rockie users improve rockie

$propose-harness-change packages improvements against the user's own local clone of rockie-codex. $upstream-contribute is the public counterpart: it dispatches a PR against saml212/rockie-codex so the next release ships the pattern to everyone.

This is the meta-loop. Researchers using rockie-codex in their own work uncover patterns that generalize — a tighter [DEAD-END] query, a hook that catches a stuck-detector edge case, a skill that helps across disciplines. The skill captures one of those, generalizes it, and opens a reviewable PR. The maintainers merge; the next user benefits.

When to run

  • The user says "upstream this", "contribute back", "anything generalizable here", "open-source this".
  • $clean finishes an audit and emits the post-audit nudge (see clean/SKILL.md → "Post-audit hook").
  • A [LEARN harness-upstream] or [LEARN cross-discipline] block was written this session and the user wants to act on it.

Run at most once per session, near the end. Don't dispatch the writer sub-agent during active work — the user wants to review the candidates before any forking happens.

Codex doesn't expose repo-defined slash commands the way Claude Code does, so the practical invocation path is $upstream-contribute or natural language ("contribute back upstream").

Method

The skill mirrors the Generator / Verifier / Updater rigor of $propose-harness-change and adds a Scout step in front (since the upstream PR is a more public artifact than a local patch).

1. Scout (this skill, in-session)

Read recent context to identify candidates:

# [LEARN] rows added this session
/usr/bin/sqlite3 ${OPENCLAW_WORKSPACE_DIR}/memory/workflow.db "
  SELECT category, rule, mistake, correction
  FROM learnings
  WHERE created_at >= datetime('now','-6 hours')
  ORDER BY created_at DESC
"

# Files changed in the last N commits
git log --since='6 hours ago' --name-only --pretty=format:'%h %s'

# Any new skill / hook / script files
git diff --name-only HEAD~5..HEAD -- '${OPENCLAW_SKILLS_DIR}/' '${OPENCLAW_WORKSPACE_DIR}/hooks/' '${OPENCLAW_WORKSPACE_DIR}/scripts/' \
  | grep -E '\.(md|sh|py)$' || true

Read the full file on GitHub · 295 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. 9d ago First seen · 295 lines · 169 tokens per session scan A ed91f89b1435

Subscribe to this mod's changes

upstream-contribute is a skill published in the GitHub repository Rockielab/rockie-codex (20 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 169 tokens to every session and 3,135 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens