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-proposenpx skills add chhuax/praxis-devos --skill openspec-proposegit 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-propose)<a href="https://agentmods.dev/skills/chhuax/praxis-devos/openspec-propose"><img src="https://agentmods.dev/badge/skills/chhuax/praxis-devos/openspec-propose.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.01188 |
| Opus 5 | $0.00022 | $0.00594 |
| Sonnet 5 | $0.00009 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
openspec-propose 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 4d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a new OpenSpec change and push it toward apply-ready whenever possible.
Core Positioning
- OpenSpec owns the change, schema, artifact dependencies, status, instructions, and readiness
- Superpowers owns requirement convergence and task breakdown
- Final outputs must remain only inside the current change directory
Capability Routing
- If the input is still vague, the boundaries are unstable, or multiple reasonable approaches exist, use
superpowers:brainstormingfirst - When generating
tasks.md, default tosuperpowers:writing-plans - In the propose stage,
writing-plansis only for the entiretasks.md
Input
The user should provide at least one of the following:
- A change name
- A description of what they want to build or fix
If they only provide a description, derive a kebab-case name from it.
Common trigger phrases include:
- "Write an OpenSpec proposal / change proposal"
- "Help me fill in the spec / design doc / tasks"
- "Break this change request into executable tasks"
- "Complete the OpenSpec artifacts so implementation can begin"
Execution Steps
1. Determine the change name
- If the name and goal are already clear, use them directly
- Otherwise, first decide whether
superpowers:brainstormingis needed - After convergence, determine the kebab-case change name
2. Check whether a change with the same name already exists
If a change with the same name already exists:
- Do not overwrite it
- Let the user decide whether to continue the existing change or use a new name
3. Enter an isolated workspace
Before creating the change, prefer calling superpowers:using-git-worktrees.
If you are already in a suitable isolated worktree, continue directly.
4. Create the change and read its status
Run:
openspec new change "<name>"
openspec status --change "<name>" --json
Read:
applyRequiresartifacts
The goal is to prioritize the artifact set required to make the change apply-ready.
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.
- 4d ago First seen · 145 lines · 43 tokens per session scan A 921662c75ba9
openspec-propose 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 1,188 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…