Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add corezoid/corezoid-ai-plugin --skill plan-to-issuesgit clone --depth 1 https://github.com/corezoid/corezoid-ai-pluginWrote 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/corezoid/corezoid-ai-plugin/plan-to-issues)<a href="https://agentmods.dev/skills/corezoid/corezoid-ai-plugin/plan-to-issues"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/plan-to-issues/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/corezoid/corezoid-ai-plugin/plan-to-issues"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/plan-to-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 139 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 275 Skill grants unrestricted tool access without appropriate constraints. An agent with unfettered tool access can perform arbitrary actions including file modification, network requests, and code execution.Fix: Restrict tool access to only the tools required for the skill's stated purpose. Use an explicit allowlist rather than granting blanket access.
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.00176 | $0.02401 |
| Opus 5.5 | $0.00070 | $0.00960 |
| Sonnet 5.5 | $0.00035 | $0.00480 |
| Haiku 4.5 | $0.00018 | $0.00240 |
Grade B, and why
plan-to-issues scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- **Do not** open PRs, push branches, or run any code changes — this skill How it starts
The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan → GitHub Issues
Turn a plan already discussed in this conversation into a tracked set of GitHub issues. No file input, no URL fetching — the plan lives in the chat history above the invocation. Read it, split it, ship it.
Repo is fixed: corezoid/corezoid-ai-plugin (this project). All gh commands
run against the current repo — do not pass --repo.
Non-negotiables
- English only. Every issue — title, body, labels, milestone title and description — MUST be written in English, regardless of the language the plan was discussed in. Translate the plan as you split it. This is non-negotiable: never publish Russian, Ukrainian, or any other language to GitHub. If a term is a project-specific proper noun (node type name, file path, CLI flag, tool name) keep it verbatim; everything else is English prose.
- Create immediately. The user has pre-authorised issue creation for this skill. Do not ask "shall I create these?" Do the work and report what was created.
- Every child issue is self-contained — a coding agent must be able to open the issue and start work with zero extra context. That means: goal, motivation, files/areas, acceptance criteria, verification, and links to related tasks are all inside the body.
- Never invent tasks. If the plan is vague on a point, mark it in the
issue as
> ⚠ Assumption:rather than silently filling gaps. - Never post secrets or internal URLs into issue bodies. Redact if the chat history contains any.
Workflow
1. Extract the plan from context
Scroll the current conversation for the plan. Signals: a numbered list of steps, a bulleted roadmap, a "TODO / next steps" block, or a design outline the user explicitly called a plan. If there are competing plans, use the most recent one the user endorsed.
If you truly can't find a plan in the context, stop and ask the user to paste it — do not fabricate.
2. Split into logical tasks
Each task should be:
- Independently shippable — mergeable as its own PR.
- Bounded — a coding agent can finish it in one focused sitting.
- Ordered by dependency — if B needs A merged first, list A first and record the dependency in B.
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 · 289 lines · 176 tokens per session scan B 12b10d808b37
plan-to-issues is a skill published in the GitHub repository corezoid/corezoid-ai-plugin (74 stars, last pushed 2d ago), licensed MIT. It adds 176 tokens to every session and 2,401 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
manage-taskboard
Manage Codex Taskboard issues and taskctl setup when the request names Codex Taskboard, e-taskboard, or taskctl, or the conversation already establishes that board as the target. Not for GitHub, Phabricator, other external trackers, or unrelated product docs.
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
workspace
Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
unharness
Safely leave Citadel using the active adoption receipt. Produces a no-write, reviewable plan, preserves a portable archive, removes only exact owned material, and reports modified or externally registered surfaces as retained or unknown. Legacy installs must be imported before exact leave is claimed.
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…