skillshare is a command-line tool that keeps AI coding-agent skills, agents, rules, commands, prompts, and other file-based resources synchronized from one source across many AI CLI tools. Individuals and teams use it to share and manage these resources across projects and organizations. The catalogue entries are skillshare commands and skills.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/runkids/skillsharenpx agentmods add skills/runkids/skillshare/skillshare-changelogWrote 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/runkids/skillshare/skillshare-changelog)<a href="https://agentmods.dev/skills/runkids/skillshare/skillshare-changelog"><img src="https://agentmods.dev/badge/skills/runkids/skillshare/skillshare-changelog/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/runkids/skillshare/skillshare-changelog"><img src="https://agentmods.dev/badge/skills/runkids/skillshare/skillshare-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00134 | $0.01369 |
| Opus 5.5 | $0.00054 | $0.00548 |
| Sonnet 5.5 | $0.00027 | $0.00274 |
| Haiku 4.5 | $0.00013 | $0.00137 |
Grade A, and why
skillshare-changelog 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 21d 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review or generate a user-facing changelog entry. Prefer the open Release Please PR and its manifest version for an upcoming release. For historical work, $ARGUMENTS specifies the requested tag or commit range.
Scope: This skill updates CHANGELOG.md and syncs the website changelog (website/src/pages/changelog.md). It does NOT generate RELEASE_NOTES, choose a new version, or handle the full release workflow — use /release for that.
Before acting, run python3 scripts/ai-context.py release. That topic is the source of truth for authorization, changelog content and synchronization rules; this skill retains the entry-generation workflow.
Workflow
Step 1: Determine Version Range
For an upcoming release, work on the Release PR branch and read .github/release-please-manifest.json. Verify the latest published tag and use its range to the Release PR head. Keep the proposed version; this skill does not authorize a version change. Tags may exist for unpublished drafts, so do not assume the highest local tag is the latest published release.
For historical work, use the user-requested tags or range.
Step 2: Collect Commits
git log <previous-published-tag>..<release-pr-head-or-requested-tag> --oneline --no-merges
Review the generated Release Please entry before writing. Preserve useful manual examples and migration notes. Do not add a second entry for the same version.
Step 3: Categorize Changes
Group commits by conventional commit type:
| Prefix | Category |
|---|---|
feat |
New Features |
fix |
Bug Fixes |
perf |
Performance |
| breaking change | Breaking Changes and migration notes |
revert |
Reverts, when user-visible |
Exclude test-only, CI-only, pure refactoring, documentation-only and internal maintenance entries from published notes.
Step 4: Read Existing Entries for Style Reference
Before writing, read the most recent 2-3 entries in CHANGELOG.md to match the established tone and structure. The style evolves over time — always match the latest entries, not a hardcoded template.
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.
- 21d ago Changed · +6 lines 671f4eea03f5
- 28d ago Changed · -3 lines bae41c2cc0c5
- 1mo ago First seen · 144 lines · 134 tokens per session scan A 885e5e5070b8
skillshare-changelog is a skill published in the GitHub repository runkids/skillshare (2,821 stars, last pushed today), licensed MIT. It adds 134 tokens to every session and 1,369 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
cf-ship-custom
This is a version bump + ship + release operation. Run these steps BEFORE the standard cf-ship workflow.
cf-ship
Verify, commit, push, and create a PR. Triggers: "ship it", "push and create PR", "let's ship", "create a PR", "open a pull request", "ready to merge". Supports --dry-run.
release-runbook
Universal release workflow: detect project type, init versioning if needed, run tests, bump version, tag, push, and create GitHub release. Works with Python, Go, Node.js, Rust, Java, .NET, Ruby, PHP, and multi-language projects.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.