Borrowing it
Nothing to install: this file belongs to dmz2922990/LLM-Switch. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dmz2922990/LLM-Switch/main/.claude/skills/openspec-continue-change/SKILL.mdgit clone --depth 1 https://github.com/dmz2922990/LLM-SwitchWrote 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/dmz2922990/llm-switch/openspec-continue-change)<a href="https://agentmods.dev/skills/dmz2922990/llm-switch/openspec-continue-change"><img src="https://agentmods.dev/badge/skills/dmz2922990/llm-switch/openspec-continue-change.svg" alt="Measured on agentmods" 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.00039 | $0.01139 |
| Opus 5 | $0.00019 | $0.00570 |
| Sonnet 5 | $0.00008 | $0.00228 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
openspec-continue-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.
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.
- 8d ago First seen · 119 lines · 39 tokens per session scan A 7d5749400570
openspec-continue-change is a skill published in the GitHub repository dmz2922990/LLM-Switch (2 stars, last pushed 13d ago), with no licence file. It adds 39 tokens to every session and 1,139 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-31.
Other skills, from other repositories
schedule-edit
Edit a workhub schedule note (projects/ /schedules/.md) from a natural-language instruction — move or resize the bars, arrows, milestones and notes in ## Items, and adjust ## Non-working days. Use when asked to shift a phase, rebalance a plan, add or remove non-working days, or when the workhub app launches a schedule…
shared-space
Record and use a team knowledge base that lives outside the vault - a network drive, Google Drive, OneDrive or SharePoint folder. Survey mode reads the place and writes down how it is organised into projects/ /shared/; place mode says where a vault note belongs in it. Use when the user wants to register a team share…
vault-setup
Set up a machine to work with a workhub vault - check/install required software (git, Node.js, Claude Code, OpenCode), initialize the vault if needed, wire up Claude plugins, and run the OpenCode sync scripts. Use when onboarding a new machine, after a fresh vault-init, or when the harness feels half-configured.
create-work-log
A tool that turns Git activity from configured repositories into a daily or weekly work log in Markdown. Git is a system that records changes to code, including who made them and when.
manage-backlog
Add, refine, split, or reorder PBIs in the file-based product backlog in the team-shared folder. Use when the user wants to create backlog items, write user stories or acceptance criteria, estimate points, split oversized items, or tidy the product backlog.
plan-sprint
Plan a sprint - set the goal, commit backlog items into scope, and write the burndown baseline (scope.json). Use at a sprint boundary when the user wants to plan the next sprint or commit items to a sprint.