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-releaseWrote 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-release)<a href="https://agentmods.dev/skills/runkids/skillshare/skillshare-release"><img src="https://agentmods.dev/badge/skills/runkids/skillshare/skillshare-release/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-release"><img src="https://agentmods.dev/badge/skills/runkids/skillshare/skillshare-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 31 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Agent Snooping · line 75 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 87 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00077 | $0.01779 |
| Opus 5.5 | $0.00031 | $0.00712 |
| Sonnet 5.5 | $0.00015 | $0.00356 |
| Haiku 4.5 | $0.00008 | $0.00178 |
Grade A, and why
skillshare-release 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 9d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare or review a skillshare release. An optional version argument is an explicit requested version, not permission to commit, merge, tag, push, or publish.
Before acting, run python3 scripts/ai-context.py release testing. These topics are the source of truth for authorization, version policy, automation and verification.
Workflow
1. Identify the release
Inspect Git status, the latest published release and the open Release PR. Preserve unrelated work. The manifest at .github/release-please-manifest.json is the release version source; the development CLI still defaults to dev.
Pushes to main create or update a Release PR. If one is missing, report the workflow state and required repository permissions. Dispatch the Release Please workflow only when the user authorizes that external action.
For 0.x, fix and perf increment patch; feat and breaking changes increment minor. A breaking change needs migration notes. Moving to 1.0.0 requires an explicit version decision. For an override, use a Release-As: X.Y.Z commit footer or a reviewed release-as configuration value; remove a configuration override after it has been consumed. Do not edit the tracking manifest by itself to request a release.
Explicit version requests
When the user requests a version such as 0.23.3, prepare a Release-As: 0.23.3 footer on a normal development commit that will reach main before the Release PR is merged. For a batch with multiple commits, adding it once to the final commit is sufficient; the override chooses the version for the entire pending release, including the earlier changes. Intermediate versions do not need to be published.
fix: correct sync behavior
Release-As: 0.23.3
With merge or rebase-merge, preserve the footer in the development commit. With squash-merge, copy it into the final squash commit message on GitHub; do not assume the individual commit messages will be preserved. Keep the Conventional Commit subject and a blank line before the footer. If multiple pending commits request different versions, the newest override wins; inspect the pending range for conflicting requests before proceeding.
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.
- 9d ago Changed fbb313d6451c
- 13d ago Changed · +21 lines 5484fd89212e
- 15d ago Changed · -42 lines · -10 tokens per session abbb658747c9
- 22d ago Changed · -4 lines 2c448d2effa6
- 1mo ago First seen · 132 lines · 87 tokens per session scan A 36bc565a64fc
skillshare-release is a skill published in the GitHub repository runkids/skillshare (2,795 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 1,779 once invoked, about $0.0003 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.