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 skills/chhuax/praxis-devos/openspec-continue-changenpx skills add chhuax/praxis-devos --skill openspec-continue-changegit clone --depth 1 https://github.com/chhuax/praxis-devosWrote 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/chhuax/praxis-devos/openspec-continue-change)<a href="https://agentmods.dev/skills/chhuax/praxis-devos/openspec-continue-change"><img src="https://agentmods.dev/badge/skills/chhuax/praxis-devos/openspec-continue-change.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.00841 |
| Opus 5 | $0.00022 | $0.00420 |
| Sonnet 5 | $0.00009 | $0.00168 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
openspec-continue-change 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 5d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continue an OpenSpec change, but create only the next ready artifact each time.
Core Positioning
- OpenSpec owns change selection, artifact dependencies, status, and instructions
- Superpowers owns requirement convergence and task decomposition
- Advance only one artifact at a time
- The continue stage does not implement business code
Exact Skill Protocol
- When this route is matched, you must call the corresponding exact skill name
- Do not substitute a similar local skill, todo list, manual breakdown, or long-form reasoning
- If the exact skill is unavailable, report that explicitly and pause the current routing
Capability Routing
- If the current artifact depends on unclear goals, boundaries, or approaches, use
superpowers:brainstormingfirst - If the current artifact is
tasks.md, callsuperpowers:writing-plansby default - In the continue stage,
writing-plansonly serves the entiretasks.md - Do not generate
docs/superpowers/plans/...or any extra master plan
Input
You may specify a change name. If none is given, first determine which change should be continued.
Execution Steps
1. Select the change
- If the user provided a change name, use it directly
- Otherwise, run
openspec list --json - If multiple candidates exist, do not guess; let the user choose
2. Check status
Run:
openspec status --change "<name>" --json
Read:
schemaNameartifactsisComplete
If isComplete: true, show the final status and stop.
3. Choose the current ready artifact
- If any artifact has
status: "ready", create only the first one - If there is no
readyartifact, show the current status and explain that progress cannot continue yet
4. Read instructions and generate the artifact
Run:
openspec instructions <artifact-id> --change "<name>" --json
Then:
- Read dependency artifacts
- Write the file using the
templatestructure - Treat
contextandrulesas constraints - Do not copy those constraint blocks verbatim into the artifact
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.
- 5d ago First seen · 118 lines · 43 tokens per session scan A 17cff63bbc89
openspec-continue-change is a skill published in the GitHub repository chhuax/praxis-devos (21 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 841 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…