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 redhat-developer/rhdh-skills --skill openspec-bulk-archive-changegit clone --depth 1 https://github.com/redhat-developer/rhdh-skillsWrote 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/redhat-developer/rhdh-skills/openspec-bulk-archive-change)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/openspec-bulk-archive-change"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/openspec-bulk-archive-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/redhat-developer/rhdh-skills/openspec-bulk-archive-change"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/openspec-bulk-archive-change.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00080 | $0.00846 |
| Opus 5 | $0.00040 | $0.00423 |
| Sonnet 5 | $0.00016 | $0.00169 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
openspec-bulk-archive-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 9d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bulk-archive OpenSpec changes
Archive multiple parallel changes at once, resolving delta-spec conflicts between them by checking which is actually implemented rather than failing or guessing.
Steps
- Get active changes:
openspec list --json. If none, tell the user and stop. - Let the user select (multi-select, never auto-select): show each change with its schema, offer "All changes", and allow any number of selections (1+ works; 2+ is the typical case).
- Gather status for every selected change: artifact status
(
openspec status --change "<name>" --json), task completion (count- [ ]/- [x]intasks.md, or note "No tasks" if absent), and delta specs underopenspec/changes/<name>/specs/with their requirement names. - Detect spec conflicts. Build
capability -> [changes touching it]; a conflict is 2+ selected changes touching the same capability. - Resolve each conflict agentically: read each conflicting change's delta spec, search the codebase for implementation evidence, and decide — only one implemented -> sync that one; both implemented -> apply in chronological order (older first, newer takes precedence); neither implemented -> skip spec sync for that capability and warn. Record the resolution and its rationale per conflict.
- Show a consolidated status table (change, artifacts, tasks, specs, conflicts, ready/warn), with conflict resolutions and incomplete-change warnings called out beneath it.
- Confirm the batch operation with a single prompt: "Archive N changes?" offering "Archive all N", "Archive only the ready ones (skip incomplete)", or "Cancel". Make clear that choosing "all" archives incomplete changes with warnings, not silently.
- Execute per confirmed change, in the resolved order: if the change has
delta specs to sync, delegate the merge to
/openspec-sync-specs(via the Task tool,subagent_type: general-purpose, with the prompt "Invoke/openspec-sync-specsfor change ''" plus this change's resolved conflict decision from step 5) — conflict detection and resolution stay here; the merge mechanics belong to that skill. Thenmkdir -p openspec/changes/archive && mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>. Track success/failed/skipped per change; an existing archive target fails that change but does not stop the batch. - Display the final summary: archived changes with their destinations, skipped changes with the reason, failed changes with the error, and a spec sync summary (deltas synced, conflicts resolved).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 73 lines · 80 tokens per session scan A 8b54573f831f
openspec-bulk-archive-change is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed today), licensed Apache-2.0. It adds 80 tokens to every session and 846 once invoked, about $0.0004 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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…