Borrowing it
Nothing to install: this file belongs to Xceptance/neodymium. 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/Xceptance/neodymium/master/.agent/skills/openspec-sync-specs/SKILL.mdgit clone --depth 1 https://github.com/Xceptance/neodymiumWrote 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/xceptance/neodymium/openspec-sync-specs)<a href="https://agentmods.dev/skills/xceptance/neodymium/openspec-sync-specs"><img src="https://agentmods.dev/badge/skills/xceptance/neodymium/openspec-sync-specs.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.00038 | $0.01025 |
| Opus 5 | $0.00019 | $0.00513 |
| Sonnet 5 | $0.00008 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
openspec-sync-specs 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 3d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 3d ago First seen · 139 lines · 38 tokens per session scan A ea77918baec6
openspec-sync-specs is a skill published in the GitHub repository Xceptance/neodymium (87 stars, last pushed yesterday), with no licence file. It adds 38 tokens to every session and 1,025 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-09-04.
Other skills, from other repositories
omniroute
Use when an orchestrated workflow may dispatch bounded implementation through an optional local OmniRoute process.
local-coding-delegate
Optional local coding loop as a mechanical or default delegate. Use when the decider model wants a cheap local coder and a hardware probe says the host can run one.
shaft-developer
Use when starting any SHAFT testing task to select exactly one lifecycle, implementation, or tool specialist before doing the work.
work-item
Use when opening or rewriting a work item on any git-based SCM. Source-control agnostic; GitHub, GitLab, and Azure Boards are adapters only.
shaft-accessibility-testing
Use when testing web or mobile accessibility for WCAG conformance, keyboard and focus behavior, semantics, errors, or user impact.
shaft-api-testing
Use when implementing or repairing SHAFT.API tests for HTTP requests, authentication, payloads, schemas, responses, contracts, or service workflows.