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-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-archive-change)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/openspec-archive-change"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/openspec-archive-change.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Anti-Refusal · line 27 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00081 | $0.00764 |
| Opus 5 | $0.00041 | $0.00382 |
| Sonnet 5 | $0.00016 | $0.00153 |
| Haiku 4.5 | $0.00008 | $0.00076 |
Grade A, and why
openspec-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 8d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive an OpenSpec change
Move a change from active to archived, confirming completeness and offering to sync its delta specs into the long-lived main specs first.
Steps
-
Select the change. If not given, run
openspec list --json, show only active (non-archived) changes with their schema, and let the user choose. Never guess. -
Check artifact completion:
openspec status --change "<name>" --json— readschemaNameand each artifact's status. If any are notdone, show a warning listing them and confirm the user wants to proceed anyway. -
Check task completion. Read the tasks file (typically
tasks.md), count- [ ]vs- [x]. If incomplete tasks exist, warn with the count and confirm before proceeding. No tasks file means no warning needed. -
Assess delta spec sync state. Check
openspec/changes/<name>/specs/. If delta specs exist, compare each against its main spec atopenspec/specs/<capability>/spec.md, determine what would change, and show a combined summary before offering: "Sync now (recommended)" vs "Archive without syncing" (or, if already synced, "Archive now" / "Sync anyway" / "Cancel"). If the user chooses sync, delegate via the Task tool (subagent_type: general-purpose) with the prompt "Invoke/openspec-sync-specsfor change ''" plus the analyzed delta summary — then archive regardless of the sync choice made. -
Perform the archive:
mkdir -p openspec/changes/archive mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>Use the current date. If the target directory already exists, fail with an error and suggest renaming the existing archive or using a different date.
.openspec.yamlmoves with the directory automatically. -
Display a summary: change name, schema, archive location, whether specs were synced, and any warnings from steps 2-3.
Output
## Archive Complete
**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** synced to main specs / no delta specs / sync skipped
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.
- 8d ago First seen · 75 lines · 81 tokens per session scan A ec3bab509976
openspec-archive-change is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 4d ago), licensed Apache-2.0. It adds 81 tokens to every session and 764 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…