Borrowing it
Nothing to install: this file belongs to EEstevanell/codex-planning-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.
curl -O https://raw.githubusercontent.com/EEstevanell/codex-planning-kit/main/.codex/skills/align-issue-card/SKILL.mdgit clone --depth 1 https://github.com/EEstevanell/codex-planning-kitWrote 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.
[](https://agentmods.dev/skills/eestevanell/codex-planning-kit/align-issue-card)<a href="https://agentmods.dev/skills/eestevanell/codex-planning-kit/align-issue-card"><img src="https://agentmods.dev/badge/skills/eestevanell/codex-planning-kit/align-issue-card/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.
<a href="https://agentmods.dev/skills/eestevanell/codex-planning-kit/align-issue-card"><img src="https://agentmods.dev/badge/skills/eestevanell/codex-planning-kit/align-issue-card.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00040 | $0.00412 |
| Opus 5.5 | $0.00016 | $0.00165 |
| Sonnet 5.5 | $0.00008 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
align-issue-card 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 2mo 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.
What it actually says
Align Issue Card + ExecPlan
Purpose
Ensure an issue card and its ExecPlan comply with AGENTS.md and PLANS.md so the work is safe to hand to a junior developer, with no ambiguity or underspecified steps. Optimize for correctness, maintainability, and low blast radius. Avoid overengineering and speculative abstractions.
Inputs (required)
ISSUE_PATH: path to the issue card Markdown file.EXECPLAN_PATH: path to the ExecPlan Markdown file.
If either is missing or ambiguous, ask for them before proceeding.
Procedure
- Read
AGENTS.mdandPLANS.mdfrom the repo root first. - Read
ISSUE_PATHandEXECPLAN_PATHfully. - Produce output using the template at
assets/align_issue_card_rubric.md(or mimic it closely):- Compliance matrix mapped to the exact
AGENTS.md/PLANS.mdrequirements. - Gap list with severity and a junior-proofness audit (undefined terms, vague steps, missing file paths, missing validation, unclear acceptance, unresolved decisions).
- Exact proposed edits (patch-style or "replace this section with ...").
- A junior-proof Acceptance Criteria + Verification Plan with explicit commands and observable outcomes.
- Compliance matrix mapped to the exact
- Resolve ambiguities by inspecting the repo (do not ask the user unless blocked).
Notes
- Prefer making a decision (and documenting it) over leaving open questions, unless the change is truly blocked.
- If the issue card and ExecPlan disagree, make them consistent and record the rationale.
Output format
- Summary (include junior-proof gaps)
- Compliance matrix (Requirement -> Evidence -> Status -> Fix)
- Proposed edits
- Final "ready to implement" checklist
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 40 lines · 40 tokens per session scan A 89a86c0edbc5
align-issue-card is a skill published in the GitHub repository EEstevanell/codex-planning-kit (2 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 412 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-08-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…