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 firstsun-dev/skills --skill openspec-verify-changegit clone --depth 1 https://github.com/firstsun-dev/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/firstsun-dev/skills/openspec-verify-change)<a href="https://agentmods.dev/skills/firstsun-dev/skills/openspec-verify-change"><img src="https://agentmods.dev/badge/skills/firstsun-dev/skills/openspec-verify-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/firstsun-dev/skills/openspec-verify-change"><img src="https://agentmods.dev/badge/skills/firstsun-dev/skills/openspec-verify-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.00051 | $0.02251 |
| Opus 5.5 | $0.00020 | $0.00900 |
| Sonnet 5.5 | $0.00010 | $0.00450 |
| Haiku 4.5 | $0.00005 | $0.00225 |
Grade A, and why
openspec-verify-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 25d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 25d ago Changed · +13 lines · +19 tokens per session 6f92f69e8e8a
- 1mo ago First seen · 175 lines · 32 tokens per session scan A 02a810d3fb26
openspec-verify-change is a skill published in the GitHub repository firstsun-dev/skills (5 stars, last pushed 6d ago), with no licence file. It adds 51 tokens to every session and 2,251 once invoked, about $0.0002 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-09-15.
Other skills, from other repositories
gitlab-create-mr
Create GitLab merge requests from a local branch using a reviewable workflow for branch checks, GitLab host detection, diff analysis, title and description writing, and glab mr create. Use when opening a GitLab merge request, drafting or improving merge request copy, preparing a branch for review, or working across…
gitlab-mr-inline-comment
Publish a single inline comment on a GitLab merge request by anchoring it to a valid diff line with glab api. Use when Codex needs to place one review comment on a specific MR file and line, while reusing the user's existing glab authentication and stopping on invalid anchors instead of falling back to a general…
otel-go-reviewer
Review pull requests, diffs, patches, or design proposals for the open-telemetry/opentelemetry-go repository with a senior maintainer mindset. Use when changes in opentelemetry-go may affect OpenTelemetry specification compliance, repository contribution rules, changelog requirements, module versioning boundaries, API…
code-review
Request or perform a git-backed code review for a defined diff or SHA range using implementation context and requirements. Use when finishing a task, completing a major feature, preparing to merge, or when you need a fresh review before proceeding.
opentelemetry-go-reviewer
High-bar review for changes in open-telemetry/opentelemetry-go with strict standards for correctness, compatibility, and performance.
interactive-human-review
An interactive review process that guides a person through a checklist and questions after a large change or during a detailed review.