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/intent-driven-dev/intent-driven-template/openspec-bulk-apply-changenpx skills add intent-driven-dev/intent-driven-template --skill openspec-bulk-apply-changegit clone --depth 1 https://github.com/intent-driven-dev/intent-driven-templateWhat 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.00030 | $0.01281 |
| Opus 5 | $0.00015 | $0.00641 |
| Sonnet 5 | $0.00006 | $0.00256 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
openspec-bulk-apply-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 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Bulk Apply
Apply multiple active OpenSpec changes by creating isolated worktrees, dispatching delegated apply flows in parallel subagents, running verification in each flow, and reporting back without merging or archiving.
REQUIRED SUB-SKILL: Use openspec-git-discipline before any apply or worktree workflow.
When to Use
- More than one active OpenSpec change exists
/opsx-bulk-applywas invoked without an explicit single-change target- The user wants multiple changes applied in parallel
- The user asks to apply all active OpenSpec changes
Do not use bulk mode when only one candidate change remains. Stop and tell the user to use /opsx-apply <change> instead.
Steps
-
Get candidate changes
Run:
openspec list --json- If command input included change names, limit analysis to those changes.
- If fewer than 2 active candidate changes remain, stop and tell the user to use
/opsx-apply <change>. - Do not ask the user to choose one change when 2 or more candidates remain and the request is clearly bulk apply.
-
Run git discipline checks
For each candidate change, verify apply is allowed before creating worktrees:
- Run
git status --short. - Verify
openspec/changes/<change>/has no uncommitted proposal files. - Verify the proposal change exists on
mainbefore applying from any branch or worktree.
If any candidate fails the gate, exclude it from execution and report the reason. If fewer than 2 executable candidates remain, stop and report that bulk apply is not appropriate.
- Run
-
Collect change context
For each executable candidate change:
openspec status --change "<name>" --json openspec instructions apply --change "<name>" --jsonThen:
- Read all listed
contextFiles. - Read the tasks artifact and summarize pending work.
- Note the implementation scope needed by the delegated apply flow.
- Exclude blocked or all-done changes from execution and include them in the final report.
- Read all listed
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 · 149 lines · 30 tokens per session scan A 7927d7287f2f
openspec-bulk-apply-change is a skill published in the GitHub repository intent-driven-dev/intent-driven-template (121 stars, last pushed 8d ago), licensed MIT. It adds 30 tokens to every session and 1,281 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
mermaid
Create, validate, and repair Mermaid.js diagrams. Use when generating flowcharts, sequence, class, ER, state, or Gantt diagrams, or any visualization.
teach-me
Turn a 'teach me X' request into a single interactive HTML lesson, rendered Arcade-first, by emitting a lesson data model and assembling it with rp1 tooling.
artifact-templates
Agent-only canonical output templates for rp1 artifacts. Load when producing structured markdown to ensure format consistency and routing metadata.
deep-research
Autonomous deep research on codebases and technical topics with structured report output via map-reduce explorer architecture.
generate-user-docs
Synchronizes user-facing documentation with the current knowledge base through validate -> stale gate -> scan -> approval -> process orchestration.
markdown-preview
Generate browser-viewable HTML previews from markdown, plain text, and Mermaid diagrams. Auto-validates, styles, and opens in browser.