What is maintain-dual-target?

A maintenance workflow for keeping a plugin's Claude Code and Codex versions synchronized. It tracks which side is the source of truth and reviews changes to commands, skills, agents, and hooks.

Use it after adding or changing plugin commands, skills, agents, or hooks when the plugin targets both Claude Code and Codex.

It prevents the two plugin versions from drifting apart after incremental edits and rejects unapproved generated-side changes.

maintain-dual-target — Skill for Claude Code by IvanLutsenko

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-plugins

agentmods

npx agentmods add skills/ivanlutsenko/awac-ai-agent-plugins/maintain-dual-target

Made for: Claude Code.

Or install plugin-cross-port, the plugin that ships this one along with the rest of its 4 skills, 1 command.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/maintain-dual-target/github.svg)](https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/maintain-dual-target)

Your own site

<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/maintain-dual-target"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/maintain-dual-target/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/maintain-dual-target"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/maintain-dual-target.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,037 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.

Model	Per session	Once invoked
Fable 5.1	$0.00041	$0.01037
Opus 5.5	$0.00016	$0.00415
Sonnet 5.5	$0.00008	$0.00207
Haiku 4.5	$0.00004	$0.00104

Measured 1mo ago against content hash a2f110031163, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

maintain-dual-target 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 1mo 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.

plugins/plugin-cross-port/skills/maintain-dual-target/SKILL.md · 136 lines

How it starts

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

Maintain Dual-Target Plugin

Keep attached plugins synchronized between Claude Code and Codex after incremental changes.

Source of truth

Source of truth is explicit:

.plugin-cross-port.marketplace.json records the canonical marketplace.
Each plugin .plugin-cross-port.json records plugin-level source_of_truth.
Mixed repositories are valid: one plugin can be Claude Code-first and another Codex-first.
Generated-side staged edits are rejected unless explicitly marked manually_maintained.

When to activate

Commands were added, removed, or edited in commands/
New skills were added to skills/
agents/ changed (new agent, description update)
Hooks changed in plugin.json
User says "sync Codex", "update dual-target", "re-run cross-port"

Workflow

Step 1 — Read state

Read .plugin-cross-port.marketplace.json
Read <plugin-path>/.plugin-cross-port.json
Read the authoritative manifest for the plugin source
Run marketplace check before switching source

Step 2 — Diff commands

Prefer the deterministic CLI:

python3 plugins/plugin-cross-port/scripts/cross_port.py marketplace sync
python3 plugins/plugin-cross-port/scripts/cross_port.py marketplace check
python3 plugins/plugin-cross-port/scripts/cross_port.py \
  plugin attach plugins/example --source codex
python3 plugins/plugin-cross-port/scripts/cross_port.py \
  plugin switch-source plugins/example --to claude-code

Step 3 — Check `manually_maintained`

If .plugin-cross-port.json lists a generated file as manually_maintained, skip overwriting it. Emit a reminder: "Manually maintained: - review manually."

Step 4 — Strict mode check

Agents are auto-converted to skills/generated-from-agents/, so only hooks can be unresolved. If --strict or the user said "strict mode":

Any unresolved hook that has no Codex equivalent causes a hard stop:

"Strict mode: unresolved hooks detected — update .plugin-cross-port.json decisions before continuing."

Read the full file on GitHub · 136 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.

1mo ago First seen · 136 lines · 41 tokens per session scan A a2f110031163

Subscribe to this mod's changes

maintain-dual-target is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (3 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 1,037 once invoked, about $0.0002 per session on Opus 5.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-09-05.

Building agents

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

systematic-debugging

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

obra/superpowers · 21 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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 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