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.
git clone --depth 1 https://github.com/catlog22/Claude-Code-WorkflowWrote 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/commands/catlog22/claude-code-workflow/convert-to-plan)<a href="https://agentmods.dev/commands/catlog22/claude-code-workflow/convert-to-plan"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/convert-to-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/commands/catlog22/claude-code-workflow/convert-to-plan"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/convert-to-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.00019 | $0.06042 |
| Opus 5.5 | $0.00008 | $0.02417 |
| Sonnet 5.5 | $0.00004 | $0.01208 |
| Haiku 4.5 | $0.00002 | $0.00604 |
Grade A, and why
convert-to-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 — 721 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Mode
When --yes or -y: Skip confirmation, auto-create issue and bind solution.
Issue Convert-to-Plan Command (/issue:convert-to-plan)
Overview
Converts various planning artifact formats into issue workflow solutions with intelligent detection and automatic binding.
Supported Sources (auto-detected):
- lite-plan:
.workflow/.lite-plan/{slug}/plan.json - workflow-session:
WFS-xxxID or.workflow/active/{session}/folder - markdown: Any
.mdfile with implementation/task content - json: Direct JSON files matching plan-json-schema
Quick Reference
# Convert lite-plan to new issue (auto-creates issue)
/issue:convert-to-plan ".workflow/.lite-plan/implement-auth-2026-01-25"
# Convert workflow session to existing issue
/issue:convert-to-plan WFS-auth-impl --issue GH-123
# Supplement existing solution with additional tasks
/issue:convert-to-plan "./docs/additional-tasks.md" --issue ISS-001 --supplement
# Auto mode - skip confirmations
/issue:convert-to-plan ".workflow/.lite-plan/my-plan" -y
Command Options
| Option | Description | Default |
|---|---|---|
<SOURCE> |
Planning artifact path or WFS-xxx ID | Required |
--issue <id> |
Bind to existing issue instead of creating new | Auto-create |
--supplement |
Add tasks to existing solution (requires --issue) | false |
-y, --yes |
Skip all confirmations | false |
Core Data Access Principle
⚠️ Important: Use CLI commands for all issue/solution operations.
| Operation | Correct | Incorrect |
|---|---|---|
| Get issue | ccw issue status <id> --json |
Read issues.jsonl directly |
| Create issue | ccw issue init <id> --title "..." |
Write to issues.jsonl |
| Bind solution | ccw issue bind <id> <sol-id> |
Edit issues.jsonl |
| List solutions | ccw issue solution <id> --brief |
Read solutions/*.jsonl |
Solution Schema Reference
Target format for all extracted data (from solution-schema.json):
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 · 721 lines · 19 tokens per session scan A d9f7524cd738
convert-to-plan is a command published in the GitHub repository catlog22/Claude-Code-Workflow (2,124 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 6,042 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-30.
Other commands, from other repositories
session-list
List recent sessions from the project ledger and offer to view one.
jira
Retrieve a Jira ticket, analyze requirements, update status, or add comments. Uses the jira-integration skill and MCP or REST API.
wtfp:contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.
gofer_hydrate
Reverse-engineer specification from existing code (Hydration).
gofer:check-workspace
Check whether this repo is initialized for Gofer and explain any missing or stale scaffold.
bulk-import-issues
Command "bulk-import-issues" from qdhenry/Claude-Command-Suite, covering bulk-import-issues, system, instructions, examples and basic bulk import.