Beads Task Memory
gastownhall/beads
Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.
A skill your agent uses when work moves between Claude Code and Codex, a session resumes from a handoff, or an agent may rewrite an existing implementation.
Install Cross Harness Continuation
$ npx skills add AnastasiyaW/codex-claude-code-config --skill cross-harness-continuation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config cross-harness-continuation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/operational/cross-harness-continuation .claude/skills/cross-harness-continuation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cross-harness-continuation" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/cross-harness-continuation into .claude/skills/cross-harness-continuation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-harness-continuation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/cross-harness-continuationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill cross-harness-continuation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config cross-harness-continuation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/operational/cross-harness-continuation .agents/skills/cross-harness-continuation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cross-harness-continuation" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/cross-harness-continuation into .agents/skills/cross-harness-continuation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-harness-continuation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill cross-harness-continuation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config cross-harness-continuation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/operational/cross-harness-continuation .cursor/skills/cross-harness-continuation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cross-harness-continuation" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/cross-harness-continuation into .cursor/skills/cross-harness-continuation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-harness-continuation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/AnastasiyaW/codex-claude-code-config.git --path skills/operational/cross-harness-continuation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill cross-harness-continuation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config cross-harness-continuation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/operational/cross-harness-continuation .gemini/skills/cross-harness-continuation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cross-harness-continuation" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/cross-harness-continuation into .gemini/skills/cross-harness-continuation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-harness-continuation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install AnastasiyaW/codex-claude-code-config cross-harness-continuationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add AnastasiyaW/codex-claude-code-config --skill cross-harness-continuation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/operational/cross-harness-continuation .github/skills/cross-harness-continuation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cross-harness-continuation" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/cross-harness-continuation into .github/skills/cross-harness-continuation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-harness-continuation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill cross-harness-continuation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config cross-harness-continuation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/operational/cross-harness-continuation .opencode/skills/cross-harness-continuation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cross-harness-continuation" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/cross-harness-continuation into .opencode/skills/cross-harness-continuation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-harness-continuation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cross-harness-continuation- GitHub stars
- 154
- Token cost
- ~1.2k tokens
- SKILL.md length
- 568 words
- Files
- 2 (incl. references)
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when work moves between Claude Code and Codex, a session resumes from a handoff, or an agent may rewrite an existing implementation.
- Works in 5 steps: Read CONTINUITY.json, the newest… → Verify the baseline commit, branch,… → Make one focused continuation change.… → …
- Work moves between Claude Code and Codex
- SKILL.md covers Operating contract, Required sequence, Replan boundary and Plugin cleanup, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Cross Harness Continuation is an agent skill from AnastasiyaW/codex-claude-code-config. Use when work moves between Claude Code and Codex, a session resumes from a handoff, or an agent may rewrite an existing implementation. Loads the shared CONTINUITY.json contract, preserves accepted decisions, checks Git baseline and scope, and requires explicit replan mode for intentional redesign. Do NOT use for fresh work with no prior agent's decisions to preserve, for a single-harness session that no one else is continuing, or as a general handoff-writing helper (see the session-handoff rule); this skill…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/CONTINUITY.example.json`).
It sits in Agent Workflows, covering Session handoff. It works with Git. The repository describes itself as: Claude Code, Codex, and multi-agent configuration system: principles, hooks, skills, and workflow patterns for AI-assisted development. The licence is MIT.
When your agent uses it
- Work moves between Claude Code and Codex
- A session resumes from a handoff
- An agent may rewrite an existing implementation
- Fresh work with no prior agents decisions to preserve
Example prompts
- “/cross-harness-continuation”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read CONTINUITY.json, the newest handoff, AGENTS.md/CLAUDE.md, and
- Verify the baseline commit, branch, dirty paths, and the claimed files.
- Make one focused continuation change. Use Edit for existing files. Do not
- Run the smallest relevant test, then the independent verifier for a
- Update the contract with what was preserved, what changed, what failed, and
What it can do on your machine
Read from SKILL.md and the folder at commit 67709af. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cross Harness Continuation loads about 1.2k tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 154 tokens; SKILL.md has 568 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from AnastasiyaW/codex-claude-code-config at commit 67709af, republished under its MIT licence (© AnastasiyaW). 568 words, ~1,210 tokens.
Download SKILL.mdSave it as
.claude/skills/cross-harness-continuation/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- cross-harness-continuation
- description
- Use when work moves between Claude Code and Codex, a session resumes from a handoff, or an agent may rewrite an existing implementation. Loads the shared CONTINUITY.json contract, preserves accepted decisions, checks Git baseline and scope, and requires explicit replan mode for intentional redesign. Do NOT use for fresh work with no prior agent's decisions to preserve, for a single-harness session that no one else is continuing, or as a general handoff-writing helper (see the session-handoff rule); this skill governs the contract between agents, not the notes one agent leaves itself.
Cross-Harness Continuation
Use this skill when a task continues after another agent, especially when the handoff is Claude -> Codex, Codex -> Claude, or a plugin has already received several partial fixes.
Operating contract
The repository is the source of truth for code. The continuation contract is the source of truth for intent that Git cannot express:
<repo>/.claude/continuity/CONTINUITY.json
The canonical shape is in references/CONTINUITY.example.json. It must contain:
mode:continuationfor incremental work,newfor greenfield work;baseline: branch, commit, and paths that were already dirty at handoff;scope.files: the files explicitly claimed for the current slice;preserve: accepted design decisions and invariants;do_not_redo: approaches already tested or deliberately rejected;verification: commands and evidence status;scope.enforceandscope.protect_unlistedwhen the slice must be strict.
Required sequence
- Read
CONTINUITY.json, the newest handoff,AGENTS.md/CLAUDE.md, and the current Git status. Treat the live checkout as authoritative over stale prose. - Verify the baseline commit, branch, dirty paths, and the claimed files. Preserve existing changes unless a test or the contract proves they are wrong.
- Make one focused continuation change. Use
Editfor existing files. Do not replace a whole file merely because another implementation is easier to write. - Run the smallest relevant test, then the independent verifier for a non-trivial or cross-module change. Record commands and outcomes in the contract or handoff.
- Update the contract with what was preserved, what changed, what failed, and the single next step. Commit a clean, descriptive checkpoint when the project workflow allows it.
Replan boundary
Replanning is valid when measured evidence shows the current design is wrong, the requirements changed, or an explicit user decision authorizes a redesign. Declare it in the process that launches the agent:
AGENT_CONTINUITY_MODE=replan
AGENT_CONTINUITY_REASON=<specific evidence and intended redesign>The reason is required. Without it, the guard blocks whole-file overwrites, out-of-scope edits, and near-whole-file replacements. A replan must also be recorded in the decision log/handoff; an environment flag alone is not proof.
Show full SKILL.md (254 more words)Show less
Plugin cleanup
Do not revert a plugin because its code “looks different”. First classify the diff as intentional, unverified, or conflicting; reconstruct the baseline from Git; run the plugin's focused tests and a fresh read-only verifier; then repair only confirmed regressions. Keep the old implementation available through Git or an isolated worktree until the replacement passes its acceptance checks.
Gotchas
- A handoff without baseline and changed-file facts is context, not a merge contract. Do not infer scope from prose alone.
- A clean Git tree does not prove semantic compatibility. Run the focused test and inspect the dependency boundary before declaring continuation complete.
- Parallel agents need isolated worktrees and an integration verifier; this skill protects serial handoff and cannot resolve a concurrent merge for you.
CONTINUITY.jsonis intentionally small. Put long research and transcripts in the private archive or project docs and link them from the contract.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
No CONTINUITY.json found | The prior session left only prose handoff | Create the contract from the current Git baseline before editing existing code |
scope violation | The task expanded beyond the claimed slice | Finish the slice or update scope with a recorded reason |
blocks Write over existing tracked file | Whole-file overwrite would erase prior intent | Use a focused Edit, or explicitly enter replan mode |
near-whole-file replacement | An edit is acting like a rewrite | Split the edit and test each step, or replan with evidence |
| Claude and Codex disagree | No shared decision/evidence was recorded | Re-read preserve, do_not_redo, tests, and Git; do not “pick a side” by intuition |
© AnastasiyaW, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/operational/cross-harness-continuation of AnastasiyaW/codex-claude-code-config.
- SKILL.md
- references/CONTINUITY.example.json
Open the folder on GitHubat commit 67709af
Compare with similar skills
Cross Harness Continuation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cross Harness Continuation this skillAnastasiyaW/codex-claude-code-config | 154 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Beads Task Memorygastownhall/beads | 28k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Session History Searchslopus/happy | 24k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Codewhale Session Handoffcodewhale-hq/Codewhale | 41k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Auditopenwpm/OpenWPM | 1.4k | — | ~676 | Automated safety check: Pass | Custom licence | |
| MemorixAVIDS2/memorix | 829 | — | ~516 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Session History Search
slopus/happy
Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.
Codewhale Session Handoff
codewhale-hq/Codewhale
Writes a paste-ready handoff for the next agent session, opening with a state-check command block and separating done, suspected and blocked work.
Audit
openwpm/OpenWPM
A skill your agent uses when stuck, confused, or disoriented in a crosslink-tracked project — dumps the full context (session state, active issue, locks, blockers, hook config, git state, project…
Memorix
AVIDS2/memorix
A skill your agent uses when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
Session Catchup and Handoff
poshan0126/dotclaude
Rebuilds working context after /clear by reading a handoff note and the branch's git state, or writes that handoff note before a session ends.
More from AnastasiyaW/codex-claude-code-config
All 50 skills in this repoBug Reproducer
AnastasiyaW/codex-claude-code-config
Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix.
Motion Framer
AnastasiyaW/codex-claude-code-config
A skill your agent uses when implementing Motion or Framer Motion in React/JavaScript: interactive UI components, micro-interactions, gestures, layout or page transitions, and scroll-based animation.
Proof Verify
AnastasiyaW/codex-claude-code-config
Plan-based verification - freeze acceptance criteria before building, then verify after with an independent fresh-context agent (the builder must not verify their own work).
Workflow Orchestration
AnastasiyaW/codex-claude-code-config
Написание и запуск Claude Code dynamic workflows (JS-оркестратор субагентов).
Notebooklm Grounded Research
AnastasiyaW/codex-claude-code-config
A skill your agent uses when: NotebookLM, notebooklm MCP, large documentation sets, courses, books, papers, or citation-backed research are mentioned.
Deepseek Provider Contract
AnastasiyaW/codex-claude-code-config
Validate a proposed DeepSeek API integration before any key or project context is sent: check thinking-mode tool-call history, strict-schema assumptions, bounded output, and provider data boundaries.
Related
Works with
Categories
Questions about Cross Harness Continuation
What does Cross Harness Continuation do?
A skill your agent uses when work moves between Claude Code and Codex, a session resumes from a handoff, or an agent may rewrite an existing implementation. Cross Harness Continuation is an agent skill from AnastasiyaW/codex-claude-code-config. Use when work moves between Claude Code and Codex, a session resumes from a handoff, or an agent may rewrite an existing implementation.
When should I use Cross Harness Continuation?
Cross Harness Continuation fits situations like: work moves between Claude Code and Codex; A session resumes from a handoff; an agent may rewrite an existing implementation; fresh work with no prior agents decisions to preserve.
How do I install Cross Harness Continuation in Claude Code?
Run `npx skills add AnastasiyaW/codex-claude-code-config --skill cross-harness-continuation -a claude-code`. Or copy the skill folder (skills/operational/cross-harness-continuation in AnastasiyaW/codex-claude-code-config) into .claude/skills/cross-harness-continuation in your project. Claude Code loads it when a task matches its description.
How do I install Cross Harness Continuation in Codex?
Run `npx skills add AnastasiyaW/codex-claude-code-config --skill cross-harness-continuation -a codex`. Or copy the skill folder (skills/operational/cross-harness-continuation in AnastasiyaW/codex-claude-code-config) into .agents/skills/cross-harness-continuation in your project. Codex loads it when a task matches its description.
Can I use Cross Harness Continuation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AnastasiyaW/codex-claude-code-config --skill cross-harness-continuation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-harness-continuation, .gemini/skills/cross-harness-continuation, .github/skills/cross-harness-continuation and .opencode/skills/cross-harness-continuation in your project.
What does Cross Harness Continuation need to run?
SKILL.md names no scripts, command-line tools or credentials: Cross Harness Continuation is instructions for the agent only.
Does Cross Harness Continuation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cross Harness Continuation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cross Harness Continuation use?
Cross Harness Continuation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cross Harness Continuation use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 219 tokens, read only when the agent opens those files.
What are the alternatives to Cross Harness Continuation?
Skills that share tags, products or a category with Cross Harness Continuation: Beads Task Memory (gastownhall/beads, 28k stars), Session History Search (slopus/happy, 24k stars), Codewhale Session Handoff (codewhale-hq/Codewhale, 41k stars) and Audit (openwpm/OpenWPM, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cross Harness Continuation?
AnastasiyaW (a GitHub user) maintains it in AnastasiyaW/codex-claude-code-config, which has 154 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 9, 2026.
Source: AnastasiyaW/codex-claude-code-config on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.