OpenSpec-aware Authoring (Codex plugin) Agent Skill

Opt-in OpenSpec-mode authoring for Chorus PM workflows in Codex.

Context cost
7.4k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 29.6 kBtext throughout, nothing executable
Licence
AGPL-3.0the author’s own terms
Last change
—v0.22.1
Servers it uses
Noneruns standalone

What it does

OpenSpec-mode authoring for Chorus PM workflows in Codex. The default whenever OpenSpec is usable; consumes the resolved `## Spec Mode` (never re-detects). Scaffolds `openspec/changes/<slug>/` on disk, and mirrors Markdown files into Chorus document drafts via `chorus mcp call --arg-file` (bash `chorus-mcp-call.sh` wrapper as fallback). Required reading for the proposal, develop, and yolo skills. When OpenSpec is not the resolved mode, this skill no-ops and the caller follows the resolved mode (spec-lite or free-form).

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

collaboration

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md29.6 kB · preview
--- name: openspec-aware license: AGPL-3.0 metadata: author: chorus version: "0.22.1" category: project-management mcp_server: chorus ---
12# OpenSpec-aware Authoring (Codex plugin)
13
14This skill is a **shared sub-procedure** invoked by the Chorus stage skills (proposal, develop, yolo) whenever the user wants spec-driven authoring through the [OpenSpec CLI](https://github.com/Fission-AI/OpenSpec). It is opt-in:
15
16- Activates when the resolved spec mode is a **usable OpenSpec** (see §1): CHORUS_SPEC_MODE=openspec *or* unset, **and** CHORUS_OPENSPEC_MODE not off, an openspec/ directory at the project root, and the openspec CLI on PATH.
17- Otherwise the calling skill follows the resolved SPEC_MODE — **spec-lite** (the default when OpenSpec isn't usable) or free-form (=off).
18
19> **See also — spec-lite (the lightweight fallback):** OpenSpec (this skill) stays the default whenever it is usable. When OpenSpec is absent or disabled — or CHORUS_SPEC_MODE=lite — the mode resolves to **spec-lite**: a durable local .chorus/specs/<slug>/spec.md (never synced) + per-change dated folders <slug>/<YYYY-MM-DD>-<change-slug>/ of Chorus-typed docs mirrored 1:1 into Chorus via the same --arg-file transport. See the spec-lite skill.
20
21When you reach a point in proposal / develop / yolo where this skill is referenced, **read the value of CHORUS_OPENSPEC_ACTIVE from the SessionStart context** (see §1) and branch on it. Do not re-run the detection block — the SessionStart hook has already done it once for this session.
22
23> **Codex specifics:** the preferred document-mirror transport is the chorus CLI (chorus mcp call … --arg-file content=<file>, §2 Rule 1). The bundled chorus-mcp-call.sh wrapper is the **fallback** when chorus is not on PATH: it is Codex's stateless MCP wrapper, located at $CHORUS_PLUGIN_DIR/hooks/chorus-mcp-call.sh after resolving $CHORUS_PLUGIN_DIR with §2.1, and is invoked as chorus-mcp-call.sh <TOOL_NAME> '<JSON_ARGUMENTS>' — no mcp-tool subcommand (unlike the Claude Code variant). The Codex port has no on-disk session state; every call is self-contained.
24>
25> The helper snippets below are Bash snippets. Codex executes shell commands through the user's configured shell, which may be zsh; run multi-line helper blocks under bash -lc (or save them as a .sh script with a Bash shebang) before using json_encode_file / chorus_check_response.
26
27---
28
29## §1. Detection — already done at SessionStart
30
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md3,984 words
Files1
LicenceAGPL-3.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈170
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
7,230
on trigger
The instruction body, read only when the skill fires.
3.7%
of a 200k window
Ten skills this size would take about 37% of the window before you open a file.
050k100k150k200k context window

7.4k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 29.6 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md29.6 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The AGPL-3.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# OpenSpec-aware Authoring (Codex plugin) · 7.4k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/openspec-aware-authoring-codex-plugin/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/openspec-aware-authoring-codex-plugin" ] && { [ ! -e .claude/skills/openspec-aware-authoring-codex-plugin ] || { mv .claude/skills/openspec-aware-authoring-codex-plugin "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/openspec-aware-authoring-codex-plugin" .claude/skills/ && echo "Installed .claude/skills/openspec-aware-authoring-codex-plugin"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add chorus-aidlc/openspec-aware-authoring-codex-plugin

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/openspec-aware-authoring-codex-plugin/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/openspec-aware-authoring-codex-plugin/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/openspec-aware-authoring-codex-plugin" ] && { [ ! -e ~/.claude/skills/openspec-aware-authoring-codex-plugin ] || { mv ~/.claude/skills/openspec-aware-authoring-codex-plugin "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/openspec-aware-authoring-codex-plugin" ~/.claude/skills/ && echo "Installed ~/.claude/skills/openspec-aware-authoring-codex-plugin" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/openspec-aware-authoring-codex-plugin/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as openspec-aware in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, openspec-aware-authoring-codex-plugin.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version0.22.1
Publishedno release date on file
PriceFree
Referencechorus-aidlc/openspec-aware-authoring-codex-plugin

Versions

v0.22.1 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v0.22.1
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v0.22.1 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill