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 skills add intent-driven-dev/intent-driven-template --skill openspec-bulk-apply-changegit clone --depth 1 https://github.com/intent-driven-dev/intent-driven-templateWrote 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/intent-driven-dev/intent-driven-template/openspec-bulk-apply-change)<a href="https://agentmods.dev/skills/intent-driven-dev/intent-driven-template/openspec-bulk-apply-change"><img src="https://agentmods.dev/badge/skills/intent-driven-dev/intent-driven-template/openspec-bulk-apply-change/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/skills/intent-driven-dev/intent-driven-template/openspec-bulk-apply-change"><img src="https://agentmods.dev/badge/skills/intent-driven-dev/intent-driven-template/openspec-bulk-apply-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 39 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00030 | $0.01281 |
| Opus 5.5 | $0.00012 | $0.00512 |
| Sonnet 5.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 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 — 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.
- 1mo ago 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 (169 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,281 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 skills, from other repositories
wrap-phase
Wraps up a development phase by cleaning AGENTSYNC.md, summarizing work, and committing changes.
github
Manage GitHub via GitHub CLI (gh): repos, issues, pull requests, Actions, releases, secrets/variables, projects, gists, searches, and API access. Auto-activates on: "gh", "github cli", "github issue", "github pr", "pull request", "github actions", "workflow", "run", "github release", "release", "gh api", "github…
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
gsd-quick-batch
Batch several /gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.