Agent-Harness-Kit: Skill for Claude Code

.agents/skills/codex-agent-dispatch/SKILL.md

codex-agent-dispatch is a skill for Claude Code, Codex from Eduardo-Salvador/Agent-Harness-Kit. It costs 56 tokens per session (432 once invoked), scanned A, original, MIT.

A controlled bridge for sending implementation or review tasks to a fresh coding agent with only the approved task context.

In plain words
What is it for?
Use it to dispatch coding tasks or independent reviews, choose the required agent role and model settings, and store evidence of what happened.
Why use it?
It limits what the agent sees and records the dispatch result, making delegated work traceable and reducing accidental context leakage.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; installed under .agents/ (shared by several agents); mentions Codex.

This is Eduardo-Salvador/Agent-Harness-Kit's own configuration. It tells Claude Code and Codex how to work on Agent-Harness-Kit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Agent-Harness-Kit configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Eduardo-Salvador/Agent-Harness-Kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Eduardo-Salvador/Agent-Harness-Kit/main/.agents/skills/codex-agent-dispatch/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Eduardo-Salvador/Agent-Harness-Kit

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 codex-agent-dispatch

README.md
[![agentmods](https://agentmods.dev/badge/skills/eduardo-salvador/agent-harness-kit/codex-agent-dispatch.svg)](https://agentmods.dev/skills/eduardo-salvador/agent-harness-kit/codex-agent-dispatch)
Your own site
<a href="https://agentmods.dev/skills/eduardo-salvador/agent-harness-kit/codex-agent-dispatch"><img src="https://agentmods.dev/badge/skills/eduardo-salvador/agent-harness-kit/codex-agent-dispatch.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 432 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.00056 $0.00432
Opus 5 $0.00028 $0.00216
Sonnet 5 $0.00011 $0.00086
Haiku 4.5 $0.00006 $0.00043

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

Security

Grade A, and why

codex-agent-dispatch 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 7d 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.

.agents/skills/codex-agent-dispatch/SKILL.md · 16 lines

What it actually says

Codex agent dispatch

Follow ../../../docs/contracts/CODEX-AGENT-DISPATCH.md and ../../../adapters/codex.md. This is the executable Codex bridge from neutral role/task artifacts to a live agent context.

  1. Build a request from the pinned TASK.md, resolved harness.model-dispatch/v1, and current capability evidence. Include only the role, task SPEC, approved authority/rule references, read_set, and impact_set; never include the conversation, full plan, or broad repository context.
  2. Run agent-harness codex-dispatch <request.json> and inspect the machine-readable plan. For implementation, retain the requested specialist identity and use role:generic-specialist when no dedicated neutral executor exists. For review, force role:reviewer-integrator, a distinct identity, and fork_turns: none.
  3. When status is ready-to-dispatch, invoke the named native operation using exactly native_call.arguments, including model and reasoning effort. Do not claim dispatch before the host returns an agent/context reference.
  4. Persist the sanitized host response, then run agent-harness codex-dispatch <plan.json> --response <response.json>. Link the resulting harness.codex-agent-dispatch/v1 record from the task/graph transition before marking the child active.
  5. An implementation request with no subagent capability records sequential-fallback and runs visibly in the orchestrator context. A review request records manual-fresh-context-required; same-context review is forbidden even under fallback.
  6. Implementer and reviewer identities, contexts, packets, and dispatch evidence remain distinct. A user-visible Codex task is created only when the user explicitly requests one; the normal route is an internal subagent.
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. 7d ago First seen · 16 lines · 56 tokens per session scan A 8747a236f0f1

Subscribe to this mod's changes

codex-agent-dispatch is a skill published in the GitHub repository Eduardo-Salvador/Agent-Harness-Kit (6 stars, last pushed 3d ago), licensed MIT. It adds 56 tokens to every session and 432 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

qa

Run scalable, isolated live QA for nac development. The top-level local orchestrator must parse n (default 4), dispatch one setup worker with this skill, copy its n assignment contracts verbatim into exactly n parallel test workers with this skill, then dispatch one aggregate worker with this skill using all test…

arcee-ai/nac · 100 tokens

release

Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.

arcee-ai/nac · 53 tokens

openrig-user

Use when a specific rig command, subcommand, or flag is already known and you need its exact syntax, JSON shape, defaults, or error meaning. NOT for natural capability discovery, open-ended how-do-I questions, or choosing which OpenRig move applies.

mvschwarz/openrig · 58 tokens

triage

Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…

arcee-ai/nac · 65 tokens

forming-an-openrig-mental-model

Use when the system around you does not make sense yet: you just booted into a seat and do not know how the pieces fit; someone said rig, pod, seat, fleet, topology, or slice and you are not certain what they mean here; you are unsure what kind of rig you are in or what it is for; you do not know how skills reach you…

mvschwarz/openrig · 117 tokens

orienting-to-an-inherited-seat

Use when you have just been primed into an EXISTING seat through a planned handover — a different agent retired and handed you the seat plus its earned context — and you need a world model of what just happened to you. Covers how a handover differs from compaction and from a fresh launch, the…

mvschwarz/openrig · 207 tokens