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 agentmods add commands/xonovex/platform/plan-continuegit clone --depth 1 https://github.com/xonovex/platformWhat 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 | $0.00013 | $0.00303 |
| Opus 5 | $0.00006 | $0.00151 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
plan-continue 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 yesterday.
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
/xonovex-workflow:plan-continue - Continue Progress from Plan
Lifecycle: research → decide → create → revise ⇄ critique → accept → subplans-create → continue → update → validate
Arguments
/plan-continue [document-path]
document-path(optional): Path to plan document. Resolution order if omitted:- Check git config for associated plan (feature worktree)
- Use current conversation context - if a
/xonovex-workflow:plan-create,/xonovex-workflow:plan-research, or similar command was run earlier in this conversation, continue from that research/plan. Do NOT search for other plans. - Only if no context exists: Ask user which plan to continue
Delegation
Load the plan-guide skill (plugin xonovex-skill-plan) and perform its
continue operation with these arguments. The skill is the source of truth for
the procedure, output format, and gotchas. Do not restate them.
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.
- yesterday First seen · 36 lines · 13 tokens per session scan A d79a8aee1a1d
plan-continue is a command published in the GitHub repository xonovex/platform (5 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 303 once invoked, about $0.0001 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-31.
Other commands, from other repositories
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
deps-age
Analyze dependency freshness and maintenance activity.
test-summary
Command "test-summary" from vishnu2kmohan/mcp-server-langgraph, covering generate comprehensive test summary, 🧪 test summary generation, step 1: determine test scope, step 2: run tests and collect results and run tests with json output.
release-prep
Automated release readiness validation.
review-pr
Comprehensive PR review checklist to ensure code quality, testing, and best practices.