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 bnet47/codexicon --skill write-plangit clone --depth 1 https://github.com/bnet47/codexiconWrote 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/bnet47/codexicon/write-plan)<a href="https://agentmods.dev/skills/bnet47/codexicon/write-plan"><img src="https://agentmods.dev/badge/skills/bnet47/codexicon/write-plan/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/bnet47/codexicon/write-plan"><img src="https://agentmods.dev/badge/skills/bnet47/codexicon/write-plan.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.00023 | $0.00660 |
| Opus 5.5 | $0.00009 | $0.00264 |
| Sonnet 5.5 | $0.00005 | $0.00132 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
write-plan 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write an implementation plan and task register
Announce: "I'm using write-plan to turn SPEC.md into verifiable local tasks."
Inputs
Read root SPEC.md, relevant architecture and conventions, applicable ADRs, the current target code, and TASKS.md when present. SPEC.md is authoritative; create or amend the root TASKS.md register without silently discarding existing tasks or evidence. Do not require a separate approval turn when the current request authorizes implementation. Do not invoke Git.
Task design
- Map every acceptance criterion to at least one task and verification step.
- Order tasks by real dependency. Identify tasks that are safe to run in parallel.
- Keep tightly coupled edits in one task. Do not split work to satisfy a time or file-count quota.
- Give each task the smallest coherent file scope and name existing interfaces precisely.
- Include migrations, compatibility behavior, error paths, and tests when required by the spec.
- Include requirement and interface IDs for every task. Do not include Git, deployment, or external writes in Build tasks.
- Use the shared persisted states
TODO,ACTIVE,BLOCKED, andDONE, with dependencies and blocker reasons recorded in the register. The queue outcomes areREADY,RESUME_ACTIVE,BLOCKED,COMPLETE, andINVALID. Validate the contract and register withpython scripts/codexicon.py spec-checkandpython scripts/codexicon.py tasks-next --jsonbefore handing off.
Output
Save agent_docs/plans/[YYYY-MM-DD]-[feature-slug]-plan.md:
# Implementation Plan: [Feature]
**Spec:** [relative link]
**Date:** [YYYY-MM-DD]
## Global constraints
- [Constraint all tasks must preserve.]
## Acceptance mapping
| Criterion | Task(s) | Evidence |
|---|---|---|
| AC-1 | 1, 3 | [test or inspection] |
### Task 1: [Coherent outcome]
**Depends on:** none | Task N
**Parallel-safe with:** [task numbers or none]
**Files:** create/modify/test exact paths
**Behavior:** [complete expected behavior and error handling]
**Interfaces:** [signatures, schemas, events, or commands]
**Verification:** `[exact command]`
**Done when:** [observable completion condition]
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 Changed · +3 lines f667bfcc9537
- 1mo ago Changed · -3 tokens per session 2410ffef982a
- 1mo ago First seen · 53 lines · 26 tokens per session scan A 701f3c5344df
write-plan is a skill published in the GitHub repository bnet47/codexicon (5 stars, last pushed 20d ago), licensed MIT. It adds 23 tokens to every session and 660 once invoked, about $0.0001 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
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
make_plan
For external plan request scenarios, guides the Agent to request a clear, actionable, step-by-step plan from a stronger Agent via listagents and chatwithagent, emphasizing that the plan is executed by the requester, not by the consulted Agent.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
orchestration-team
Use when coordinating assignments, selected review boundaries, or blocked work across a rig.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…
oma-scholar
Search academic literature and generate, validate, or compare Knows paper sidecars. Use for claim/evidence analysis and literature synthesis.