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/github/spec-kit/add-community-extensionnpx skills add github/spec-kit --skill add-community-extensiongit clone --depth 1 https://github.com/github/spec-kitWhat 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.00063 | $0.01597 |
| Opus 5 | $0.00032 | $0.00798 |
| Sonnet 5 | $0.00013 | $0.00319 |
| Haiku 4.5 | $0.00006 | $0.00160 |
Grade A, and why
add-community-extension 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 yesterday.
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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Community Extension
Process an extension submission issue and add or update it in the community catalog.
When to Use
- A new
[Extension]submission issue is filed - An existing extension submits an update issue (new version, changed metadata)
- You need to add or update a community extension in
extensions/catalog.community.jsonanddocs/community/extensions.md
Procedure
1. Fetch the submission issue
Read the GitHub issue to extract all metadata:
- Extension ID, name, version, description, author
- Repository URL, download URL, homepage, documentation, changelog
- License, required spec-kit version, optional tool dependencies
- Number of commands and hooks
- Tags
2. Validate against publishing rules
Check all of the following (per extensions/EXTENSION-PUBLISHING-GUIDE.md):
| Check | How |
|---|---|
| Repository exists and is public | Fetch the repository URL |
extension.yml manifest present |
Confirm in repo file listing |
| README.md present | Confirm in repo file listing |
| LICENSE file present | Confirm in repo file listing |
| GitHub release exists matching version | Check releases on the repo page |
| Download URL is accessible | Verify it follows archive/refs/tags/vX.Y.Z.zip pattern and release exists |
| Extension ID is lowercase-with-hyphens only | Regex: ^[a-z][a-z0-9-]*$ |
| Version follows semver | Format: X.Y.Z |
| Submission checklists are all checked | Confirm in issue body |
3. Determine if this is an add or update
Search extensions/catalog.community.json for the extension ID.
- Not found → this is a new addition. Proceed to step 4.
- Found → this is an update. Proceed to step 4 but replace the existing entry in-place instead of inserting.
4. Add or update extensions/catalog.community.json
New extension: Insert the entry in alphabetical order by extension ID.
Update: Replace the existing entry in-place. Update only the fields that changed (typically version, download_url, description, provides, requires, tags, updated_at). Preserve created_at and downloads/stars from the existing entry.
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.
- yesterday First seen · 175 lines · 63 tokens per session scan A 3061dc39dfd4
add-community-extension is a skill published in the GitHub repository github/spec-kit (132,298 stars, last pushed 3d ago), licensed MIT. It adds 63 tokens to every session and 1,597 once invoked, about $0.0003 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
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
release-openspec
Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is…
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.