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 agentmods add skills/sillsdev/fieldworks/openspec-explorenpx skills add sillsdev/FieldWorks --skill openspec-exploregit clone --depth 1 https://github.com/sillsdev/FieldWorksWhat 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 | $0.00039 | $0.02157 |
| Opus 5 | $0.00019 | $0.01078 |
| Sonnet 5 | $0.00008 | $0.00431 |
| Haiku 4.5 | $0.00004 | $0.00216 |
Grade A, and why
openspec-explore 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 2d 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.
- 2d ago First seen · 291 lines · 39 tokens per session scan A 82eff33a81ba
openspec-explore is a skill published in the GitHub repository sillsdev/FieldWorks (111 stars, last pushed 4d ago), with no licence file. It adds 39 tokens to every session and 2,157 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-30.
Other skills, from other repositories
zh-article-analyzer
繁體中文文章深度分析技能。對任何中文文章進行多維度科學化剖析，產出精確到行號與段落的分析報告。 涵蓋：文體指紋（Stylometrics）、語言節奏、詞彙豐富度、引用與典故圖譜、主題動態、情感弧線、 修辭力道、文白比、成語密度等。結合 Python 量化腳本與 LLM 質性分析，產出完整的「文章指紋報告」。 當使用者提到「分析文章」、「文章風格」、「寫作分析」、「文體分析」、「文章指紋」、「語言風格」、 「修辭分析」、「文章比較」、「作者風格」、「寫法分析」，或上傳中文文章要求任何形式的語言學或 文體學分析時，務必觸發此技能。即使使用者只是問「這篇文章寫得怎樣」也應觸發。.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…