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/ninemindai/agentgem/releasenpx skills add ninemindai/agentgem --skill releasegit clone --depth 1 https://github.com/ninemindai/agentgemWhat 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.00046 | $0.00804 |
| Opus 5 | $0.00023 | $0.00402 |
| Sonnet 5 | $0.00009 | $0.00161 |
| Haiku 4.5 | $0.00005 | $0.00080 |
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 3d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cutting an AgentGem release
Core (@ninemind/agentgem) and the desktop app share one version number but are
tagged separately: vX.Y.Z (core) and desktop-vX.Y.Z (desktop). A normal release
ships both tags on the same commit.
1. Release worktree + branch
git fetch origin
git worktree add ../agentgem-worktrees/release-X.Y.Z -b release/X.Y.Z origin/main
cd ../agentgem-worktrees/release-X.Y.Z && pnpm install --frozen-lockfile
2. One release commit
Three files, one commit, message release: vX.Y.Z — core + desktop:
package.json+desktop/package.json— bump"version"in both.CHANGELOG.md— Keep-a-Changelog style, two sections inserted above the previous release:## [X.Y.Z] — \@ninemind/agentgem` (npm core) — YYYY-MM-DD(intro paragraph naming the release's themes + commit count fromgit log --oneline vPREV..origin/main | wc -l, then Added/Changed/Fixed) and## [desktop-vX.Y.Z] — desktop app — YYYY-MM-DD` (desktop-specific changes, then a one-liner noting it embeds everything in core X.Y.Z).
3. PR → merge
Push, open a PR, wait for the test (24) gate, then rebase-merge
(gh run watch <run-id> --exit-status, gh pr merge --rebase --delete-branch).
--delete-branch errors on the local delete (main is checked out in another worktree)
— the remote merge still succeeds; verify with git fetch + check origin/main.
4. Tag the main commit, then push tags
A rebase merge mints a new SHA — tagging the branch commit strands the tag off-main (this happened to v0.5.0/v0.6.0's branches; the tags were correctly placed on main).
git fetch origin
SHA=$(git log origin/main --format=%H --grep "release: vX.Y.Z" -1)
git tag -a vX.Y.Z -m "vX.Y.Z — core + desktop" "$SHA"
git tag -a desktop-vX.Y.Z -m "desktop-vX.Y.Z — core + desktop" "$SHA"
git push origin vX.Y.Z desktop-vX.Y.Z
5. What the tags trigger — and what stays manual
| Step | Trigger |
|---|---|
| Node 26 CI matrix | automatic on v* / desktop-v* push (ci.yml) |
Desktop build + GitHub release (latest*.yml for auto-update) |
automatic on desktop-v* (desktop-release.yml) |
| npm publish | manual: npm publish from the tagged checkout — prepublishOnly runs clean + build + bundle-bins |
| Website desktop-download link | manual follow-up PR pointing at desktop-vX.Y.Z |
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.
- 3d ago First seen · 66 lines · 46 tokens per session scan A d1167fb210c4
release is a skill published in the GitHub repository ninemindai/agentgem (39 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 804 once invoked, about $0.0002 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
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
release
Prepare a named version: preflight, version consistency, build/package, smoke test, checksums/notes, and release readiness. Publishing/tagging/deploy need separate authorization. Explicit-only.
release-notes
Use when asked to generate release notes, or when the /release-notes command runs — derive user-facing release notes from the change history since the last release.
promoting-dev-to-main
Use when preparing, reviewing, resolving conflicts for, or merging a CORAL release pull request from the long-lived dev branch into main.
ship-it
Code commit, PR creation, merge, and issue closure workflow via GitHub CLI (gh). Triggers after a goal (GitHub Issue) implementation is complete — commit code, push branch, create PR, merge, then close the issue. Use when the user says "提交代码", "commit and merge", "创建PR", "合入", "关闭issue", "ship-it", or when a goal…