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 AnastasiyaW/codex-claude-code-config --skill plan-to-ticketsgit clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-configWrote 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/anastasiyaw/codex-claude-code-config/plan-to-tickets)<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/plan-to-tickets"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/plan-to-tickets/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/anastasiyaw/codex-claude-code-config/plan-to-tickets"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/plan-to-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.00591 |
| Opus 5 | $0.00037 | $0.00296 |
| Sonnet 5 | $0.00015 | $0.00118 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
plan-to-tickets 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 10d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan To Tickets
Turn a large plan into small, independently executable tickets. Use this before handing a broad plan to agents, before long autonomous work, or when the user asks for tickets/issues/slices.
Output Location
If no issue tracker is explicitly selected, write local tickets under:
<project>/.agent/tickets/<YYYY-MM-DD>-<slug>/
Each ticket is one Markdown file:
TICKET-001-short-slug.md
Required Ticket Shape
Each ticket must include these headings exactly:
## Status## Parent## What To Build## Acceptance Criteria## Verification## Blocked By## Notes
## Status must contain ready-for-agent only when all acceptance criteria and verification steps are concrete.
## Acceptance Criteria must contain checklist items (- [ ] ...).
## Verification must contain at least one command, script, test, artifact check, or explicit manual-review gate.
Slicing Rules
- Prefer vertical tracer bullets: a narrow complete path through the required layers, not "all backend" then "all UI" then "all tests".
- A ticket must be independently verifiable.
- Put prefactoring first only when it makes a later slice smaller or safer.
- Keep dependencies explicit in
## Blocked By; writeNonewhen it can start immediately. - Do not include stale-prone file paths unless the path is already a stable contract or current codebase evidence.
- Do not publish external tracker issues unless the user asked for that tracker.
Workflow
- Read the plan/spec and current repo context needed to avoid fake tickets.
- Draft ticket files in dependency order.
- Run the validator:
python "$env:USERPROFILE\.claude\claude-code-config\scripts\validate_agent_tickets.py" --tickets-dir <ticket-dir>
- Fix every validator failure before claiming the ticket split is ready.
- Report the ticket directory and the count of ready tickets.
Gotchas
- Horizontal tickets overload later agents. If a ticket cannot be verified alone, split it differently.
- "Implement feature" is not an acceptance criterion. ACs must describe observable behavior or artifacts.
- "Run tests" alone is weak verification. Name the test command or the artifact that proves success.
- Do not use this to postpone work. Ticketization is for large plans; small tasks should be implemented directly.
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.
- 10d ago First seen · 66 lines · 74 tokens per session scan A a463758ffb33
plan-to-tickets is a skill published in the GitHub repository AnastasiyaW/codex-claude-code-config (149 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 591 once invoked, about $0.0004 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-30.
Other skills, from other repositories
lean-debt
Harvest every lean: comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals Lean leaves behind get tracked instead of rotting into "later means never". Use when the user says "lean debt", "/lean-debt", "what did lean defer", "list the shortcuts", "lean ledger", or "what did we mark to do…
ai-content-filter
Professional Ai Content Filter Expert skill. Integrate LLM API workflows, safe system prompt guidelines, and agentic workflows.
ai-engineer
Professional Ai Engineer skill. Integrate LLM API workflows, safe system prompt guidelines, and agentic workflows.
ai-product-manager
Professional Ai Product Manager Expert skill. Integrate LLM API workflows, safe system prompt guidelines, and agentic workflows.
embedding-architect
Professional Embedding Architect skill. Integrate LLM API workflows, safe system prompt guidelines, and agentic workflows.
eval-harness
Professional Eval Harness Expert skill. Integrate LLM API workflows, safe system prompt guidelines, and agentic workflows.