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 griffinwork40/agent-afk --skill afk-releasegit clone --depth 1 https://github.com/griffinwork40/agent-afkWrote 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/griffinwork40/agent-afk/afk-release)<a href="https://agentmods.dev/skills/griffinwork40/agent-afk/afk-release"><img src="https://agentmods.dev/badge/skills/griffinwork40/agent-afk/afk-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/griffinwork40/agent-afk/afk-release"><img src="https://agentmods.dev/badge/skills/griffinwork40/agent-afk/afk-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.00156 | $0.02685 |
| Opus 5.5 | $0.00062 | $0.01074 |
| Sonnet 5.5 | $0.00031 | $0.00537 |
| Haiku 4.5 | $0.00016 | $0.00268 |
Grade A, and why
afk-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 today.
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://agentafk.com | grep -oE 'version-pill">v[0-9.]+'` How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
afk-release
Releases are manual (docs/publish-workflow.md). The only thing that
publishes is a pushed vX.Y.Z tag, which fires .github/workflows/publish.yml
(tag-vs-package guard, lint, test, npm publish --provenance, GitHub Release).
scripts/release.mjs (pnpm release) does the bump, CHANGELOG stamp, commit,
tag, and atomic push. This skill wraps it with the checks a human used to do
by hand, plus one confirmation gate.
Run from the repo root of the agent-afk checkout. Run this skill in the
top-level session (context: load). It needs ask_question for the gate,
and forked children auto-decline that tool.
Hard rules
- Publishing to npm cannot be undone: a version number can never be reused.
Never run
pnpm releasewithout the Phase 5 confirmation, unless the arguments contain--yes. - Never force-push. Never delete, move, or re-push a tag that already reached
the remote. Never run
npm publishlocally (provenance needs the CI runner). - Never stash, reset, or discard the operator's working-tree changes to make preflight pass. Report them and stop.
- Commit messages go on stdin through a quoted heredoc (
git commit -F - <<'EOF'), never inside double quotes. - The operator's
release-boundaryPreToolUse hook blocks shell commands that look like a publish. It fires even on a read-only grep whose pattern contains the publish command text, so search workflow files with the grep tool instead of a shell grep. If it blocks Phase 6, do not route around it. End with Asking and hand the operatorpnpm release <bump>to run. - If
ghreports "multiple remotes detected", add-R griffinwork40/agent-afk.
Phase 1: Preflight (read-only, run the checks in parallel)
| # | Check | Command | Fail action |
|---|---|---|---|
| 1 | On main |
git rev-parse --abbrev-ref HEAD |
BLOCKED |
| 2 | No tracked changes (untracked ?? files are fine) |
git status --porcelain | grep -v '^??' |
BLOCKED, list the paths |
| 3 | Up to date | git fetch origin --tags, then compare git rev-parse HEAD with git rev-parse origin/main |
Behind and check 2 passed: git pull --ff-only. Ahead or diverged: BLOCKED |
| 4 | CI green on that exact SHA | gh run list --workflow ci.yml --branch main --limit 10 --json headSha,status,conclusion,databaseId,url, then pick the run whose headSha equals origin/main |
In progress: gh run watch <id> --exit-status. Missing or failed: BLOCKED with the run URL |
| 5 | No publish in flight | gh run list --workflow publish.yml --limit 1 --json status,headBranch,conclusion |
Running: wait for it or BLOCKED |
| 6 | npm matches the last tag | git describe --tags --abbrev=0 versus npm view agent-afk version |
Mismatch means the last publish never landed. Go to Recovery, do not cut a new version on top |
| 7 | Something to release | git log <last-tag>..HEAD --format='%h %s', ignoring chore(release): lines |
Empty: NOTHING-TO-RELEASE |
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.
- today First seen · 184 lines · 156 tokens per session scan A e62d0af66c56
afk-release is a skill published in the GitHub repository griffinwork40/agent-afk (62 stars, last pushed today), licensed Apache-2.0. It adds 156 tokens to every session and 2,685 once invoked, about $0.0006 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-11-01.
Other skills, from other repositories
aiox-devops
Activate Gage (devops) for GitHub Repository Manager & DevOps Specialist. Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository.
aiox-devops
GitHub Repository Manager & DevOps Specialist (Gage). Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized...
hatch3r-release
Cuts a release with version bump, changelog, tagging, and deploy verification. Use when preparing a release, cutting a version, or deploying to production.
ship-pr
Ship Skill: Creates PRs from feature branches, waits for CI, merges, and deploys using whatever mechanism the repo actually uses. MANDATORY TRIGGERS: ship, deploy, release, merge, create PR, push, go live, launch.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…