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 iampantherr/SecureContext --skill publish-github-releasegit clone --depth 1 https://github.com/iampantherr/SecureContextWrote 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/iampantherr/securecontext/publish-github-release)<a href="https://agentmods.dev/skills/iampantherr/securecontext/publish-github-release"><img src="https://agentmods.dev/badge/skills/iampantherr/securecontext/publish-github-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/iampantherr/securecontext/publish-github-release"><img src="https://agentmods.dev/badge/skills/iampantherr/securecontext/publish-github-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Tool Misuse · line 152 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00099 | $0.01669 |
| Opus 5.5 | $0.00040 | $0.00668 |
| Sonnet 5.5 | $0.00020 | $0.00334 |
| Haiku 4.5 | $0.00010 | $0.00167 |
Grade A, and why
publish-github-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 1mo 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish a GitHub release
Generic procedure for shipping a new version of a project. Reads
project-specific config from <project>/.publish-github-release-config.json
if present (see references/config-schema.md).
When to use
Trigger phrases (literal words the user might type):
- "ship v1.2.3"
- "release"
- "tag a new version"
- "publish"
- "cut a release"
- "make a new release"
- "bump version and release"
- "deploy this release to github"
Auto-detect trigger: if CHANGELOG.md has a ## [Unreleased] heading with
entries underneath, and the agent has just finished a coherent unit of work,
suggest invoking this skill.
DO NOT use this for:
- Patch increments without code changes (use
npm version patchdirectly). - Pre-release / RC builds (use the
prerelease-tagskill instead — coming in a later release). - Repos with no GitHub remote (the skill assumes
ghCLI auth and a remote namedoriginpointing at GitHub).
Procedure
Step 1 — Preflight gates
Run scripts/preflight.py. Reads project config; fails fast on:
- Working tree dirty (uncommitted changes)
- Branch is not on
main(or whateverconfig.main_branchsays) - Local is behind remote on main (would force-push)
- CI is currently red on the head commit
package.jsonversion doesn't match the previous CHANGELOG entry header
Exits 0 = ready to release. Non-zero = stop and surface the failure to the operator.
Step 2 — Bump version everywhere
Run python scripts/bump-version.py --kind {major|minor|patch} (or
--version 1.2.3 for an explicit version). Reads
config.version_files and atomically rewrites the version string in
each. Default version-bearing files:
package.json(.version)- Plus anything listed in
<project>/.publish-github-release-config.json'sversion_files. SecureContext for example lists[package.json, src/config.ts, .claude-plugin/plugin.json].
Refuses to bump if the new version is already a tag.
Step 3 — Regenerate the CHANGELOG entry
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 171 lines · 99 tokens per session scan A 0771028ae22e
publish-github-release is a skill published in the GitHub repository iampantherr/SecureContext (8 stars, last pushed 10d ago), licensed MIT. It adds 99 tokens to every session and 1,669 once invoked, about $0.0004 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-31.
Other skills, from other repositories
github-repo-care
Protocol for safely creating, publishing, releasing, auditing, and maintaining GitHub repositories: check local rules and locks, create .gitignore before the first add, run privacy checks, prepare README/i18n/banner/metadata, verify release tags and GitHub releases, and update organization profiles, llms.txt files…
github-cli
A command-line tool connection for GitHub tasks that built-in tools do not cover. It uses GitHub's command-line program to work with issues, pull requests, releases, workflows, searches, and the GitHub API.
release-docs
Diff-driven documentation sync after a release. Determines what source files changed, delegates changelog to zuvo:docs, updates only docs whose source changed. Flags: --dry-run, explicit range argument.
release
Cut a new release: group Conventional Commits since the last tag, append a CHANGELOG section, create a release commit, and add an annotated git tag. TRIGGER when the user says "cut a release", "tag a release", "release v1.2.0", "ship version 1.2.0", "create a release for 1.2.0", "bump the version to 1.2.0", "make a…
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
hotfix
Set up the branch topology for a patch release against a previously tagged version: ensures release/ . exists from the source tag, then creates hotfix/ off it. TRIGGER when the user says "hotfix v1.0.0", "patch the release", "I need to fix something in the v2 line", "create a hotfix branch", "/nyann:hotfix". Match…