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/suxrobgm/jobpilot/releasenpx skills add suxrobGM/jobpilot --skill releasegit clone --depth 1 https://github.com/suxrobGM/jobpilotWrote 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/suxrobgm/jobpilot/release)<a href="https://agentmods.dev/skills/suxrobgm/jobpilot/release"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/release.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.00790 |
| Opus 5 | $0.00013 | $0.00395 |
| Sonnet 5 | $0.00005 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
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 5d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill
Cut a new JobPilot release. Host and plugin share one version and ship from
one tag (vX.Y.Z), which triggers .github/workflows/release.yml - it builds
the terminal binaries for all RIDs, publishes the GitHub Release (the terminal
archives, which bundle the plugin tree), and syncs the plugin tree into the
claude-plugins and codex-plugins marketplaces.
Usage
The user provides a version (e.g. 2.1.0) or a bump type (major, minor,
patch). With no argument, default to a patch bump.
Context
- Version source of truth (must stay in lockstep):
apps/terminal/JobPilot.Terminal.csproj- the<Version>elementplugin/.claude-plugin/plugin.json-"version"plugin/.codex-plugin/plugin.json-"version"package.json-"version"
- Tag format:
vX.Y.Z(matches thev*trigger inrelease.yml). - Changelog:
CHANGELOG.mdat the repo root, Keep a Changelog format, newest release first. The workflow also setsgenerate_release_notes: truefor the GitHub Release.
Steps
-
Determine the new version:
- Read the current version from all four files above.
- If they differ, report the mismatch and reconcile to the highest before bumping.
- Use the user's explicit version, else compute from the bump type, else bump patch.
- Verify the new version is strictly greater than the current highest.
-
Pre-flight checks (stop and report on any failure - do not paper over):
- Working tree is clean (
git status). - Current branch is
main(or ask if on another branch). - No existing tag
vX.Y.Z(git tag -l).
- Working tree is clean (
-
Bump version: set the new version in all four files.
-
Update CHANGELOG.md (create it with a
# Changelogheader if missing):- List commits since the previous tag:
git log <prev-tag>..HEAD --oneline(all commits if no tag exists). - Prepend a
## vX.Y.Z - YYYY-MM-DDsection, grouping the changes under### Added/### Changed/### Fixedas applicable. Summarize user-facing changes in plain language; fold internal chores/refactors into one line or omit them. - Skip merge commits and the release commit itself.
- List commits since the previous tag:
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.
- 5d ago First seen · 70 lines · 26 tokens per session scan A 2bf6d6b8ba98
release is a skill published in the GitHub repository suxrobGM/jobpilot (65 stars, last pushed 5d ago), licensed MIT. It adds 26 tokens to every session and 790 once invoked, about $0.0001 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
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
new
Use when user asks to create a release, cut a release, or publish a version. Auto-detects GitHub vs GitLab vs Gitea, calculates semantic version, generates release notes from PRs/MRs or commits, shows preview for confirmation before publishing.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
ops-release
OPS on-demand: This skill should be used when the user asks to "release the plugin", "publish ops…
bump-version
Bump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version. Use when: user says 'bump version', 'update version', '更新版本', '版本 +1', or /bump-version.