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/primeintellect-ai/verifiers/releasenpx skills add PrimeIntellect-ai/verifiers --skill releasegit clone --depth 1 https://github.com/PrimeIntellect-ai/verifiersWhat 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.00017 | $0.00428 |
| Opus 5 | $0.00009 | $0.00214 |
| Sonnet 5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
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.
What it actually says
Release Verifiers
Use the next minor version by default. Use a different vX.Y.Z version when the
user specifies one. Complete only the release steps that the user authorizes.
1. Prepare main
Run the release from the main repository:
git switch main
git pull --ff-only origin main
git status --short --branch
VERSION=vX.Y.Z
Require a clean worktree. Confirm that $VERSION is absent from GitHub and
PyPI. Review pyproject.toml and require published stable dependency versions.
For example, replace any .dev, alpha, beta, or release-candidate version and
update uv.lock. Land dependency changes through the normal PR process. Pull
main again and require a clean worktree before tagging.
2. Tag latest main
git tag "$VERSION"
git push origin "refs/tags/$VERSION"
Confirm that the remote tag points to the current main commit.
3. Publish
Manually dispatch the stable release workflow:
gh workflow run publish-verifiers.yml \
--repo PrimeIntellect-ai/verifiers \
--ref main \
-f tag="$VERSION"
Monitor the new run through completion with gh run watch <run-id> --exit-status.
4. Update the release notes
After the workflow creates the public GitHub Release, read the previous stable release and use the same release-note format. Describe the changes since that release, then update the new release:
gh release edit "$VERSION" \
--repo PrimeIntellect-ai/verifiers \
--notes-file <release-notes.md>
5. Verify
Confirm that:
- PyPI lists
${VERSION#v}with a wheel and source archive. - The GitHub Release is public with both files attached.
- The release notes match the prior release format.
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 · 70 lines · 17 tokens per session scan A 626ccab42ecb
release is a skill published in the GitHub repository PrimeIntellect-ai/verifiers (4,577 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 428 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.