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 skills add runkids/skillshare-app --skill skillshare-app-releasegit clone --depth 1 https://github.com/runkids/skillshare-appWrote 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-app/skillshare-app-release)<a href="https://agentmods.dev/skills/runkids/skillshare-app/skillshare-app-release"><img src="https://agentmods.dev/badge/skills/runkids/skillshare-app/skillshare-app-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-app/skillshare-app-release"><img src="https://agentmods.dev/badge/skills/runkids/skillshare-app/skillshare-app-release.svg" alt="Reviewed on agentmods" width="80" 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.00135 | $0.01555 |
| Opus 5.5 | $0.00054 | $0.00622 |
| Sonnet 5.5 | $0.00027 | $0.00311 |
| Haiku 4.5 | $0.00014 | $0.00155 |
Grade A, and why
skillshare-app-release scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL "https://github.com/runkids/skillshare-app/releases/latest/download/latest.json?t=$(date +%s)" | jq -r .version # cache-buster: the plain URL can serve the old file for a few minutes How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release the skillshare app
The release is mostly automated. Your job is to start it at the right moment, choose the version when asked, and confirm that every part actually landed.
Before step 1, load the pipeline facts and recovery procedures:
python3 scripts/ai-context.py release. This skill only orders the steps.
Steps
1. Preflight
git fetch --tags origin
gh pr list --state open --json number,title,headRefName
gh run list --branch main --workflow ci.yml --limit 1 --json databaseId,headSha,status,conclusion
Releasing happens on GitHub, so the local working tree doesn't matter. Work from
origin/main, and don't switch branches, stash or pull over the user's local changes.
- Only the release PR should be open. Other open PRs are not in this release.
Tell the user, and ask whether to merge them first. If a PR is about to merge
and belongs in this release (for example a follow-up fix the user wants "一起上"),
wait for it to merge (
scripts/merge-pr.sh <n>). Then wait until the release PR diff lists it before you merge the release PR. Release Please updates the PR a minute or two after each push tomain. - If main's latest CI run is still in progress, wait for it with
gh run watch <id>. The release PR is opened by a bot, so CI does not run on it. Main's CI is the only check on the code being released, so don't merge on a red or unfinished run.
2. Find the release PR and settle the version
- No release PR:
- Check whether Release Please is still running
(
gh run list --workflow "Release Please" --limit 1). - If it has finished, list what is unreleased:
git log --oneline "$(git describe --tags --abbrev=0 origin/main)"..origin/main - If none of those commits is a
featorfix, there is nothing to release. Say so, and say what would make a release: merge afeat/fixPR, or useRelease-As(below). Don't invent a release.
- Check whether Release Please is still running
(
- The user named a version (e.g. "發 0.2.0"): Release Please honours a
Release-As: X.Y.Zline in a commit body onmain.- If a feature or fix PR is about to be merged anyway, put the line in its
squash body:
gh pr merge <n> --squash --admin --delete-branch --body "Release-As: 0.2.0" - Otherwise open a small PR that adds
"release-as": "0.2.0"topackages["."]in.github/release-please-config.json. - Either way, wait for the release PR to show the new version.
- If you used the config route, remove
release-asin a follow-up PR after the release. Otherwise Release Please keeps asking for that version.
- If a feature or fix PR is about to be merged anyway, put the line in its
squash body:
- Review the release PR diff (
gh pr diff <n>):- All five version fields agree.
- The CHANGELOG lists what the user expects.
- Show the user the version and the CHANGELOG entries in your update.
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.
- 12d ago Changed · +7 lines 43d5dab8628e
- 14d ago First seen · 120 lines · 135 tokens per session scan A b7c8691f291a
skillshare-app-release is a skill published in the GitHub repository runkids/skillshare-app (24 stars, last pushed yesterday), licensed MIT. It adds 135 tokens to every session and 1,555 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.
Other skills, from other repositories
app-release
Use when the user asks to release a new version, ship a build, or publish a Skill Zoo release. Also use when a tag push results in Homebrew 404 errors or missing artifact failures.
npm-trusted-publishing
Use when setting up npm publishing with GitHub Actions - provides trusted publishing with OIDC, provenance attestations, and monorepo configuration.
npm-release
Use when publishing or preparing to publish an npm package from this repository, especially the Skill Zoo CLI package under packages/cli. Also use when npm publish fails because of duplicate versions, npm authentication, browser authentication, dist-tag propagation, tarball contents, bin entry issues, or…
deployment-rules
Release/deployment standards — semantic-release, commitlint, version sync, the updater. Load for /prepare-release and changes to release.config.mjs / commitlint / workflows / version files. Owned by project-steward.
npm-release
Guide for setting up automated npm package releases via GitHub Actions using Trusted Publishing (OIDC). Use when creating release workflows, publishing to npm, or troubleshooting CI/CD publish failures.
gitlab-cli
Reference guide for GitLab CLI (glab) commands. Use when running glab commands for issues, merge requests, pipelines, releases, or CI/CD operations, or when the user asks about GitLab CLI syntax.