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/dhofheinz/open-plugins/afknpx skills add dhofheinz/open-plugins --skill afkgit clone --depth 1 https://github.com/dhofheinz/open-pluginsWrote 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/dhofheinz/open-plugins/afk)<a href="https://agentmods.dev/skills/dhofheinz/open-plugins/afk"><img src="https://agentmods.dev/badge/skills/dhofheinz/open-plugins/afk.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.00046 | $0.00549 |
| Opus 5 | $0.00023 | $0.00275 |
| Sonnet 5 | $0.00009 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
afk 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 4d 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
AFK Mode Skill
Manage AFK (Away From Keyboard) mode with tiered tool access and session tracking.
Operations
- Enable AFK mode - Activate AFK with tiered tool access (full/plan/research/monitor)
- Disable AFK mode - Turn off AFK and resume normal operation
- Check status - View current AFK status and statistics
- Review session - Review planning documents and blocked actions
Routing
Parse $ARGUMENTS to determine the operation:
| First Word | Operation | Description |
|---|---|---|
full |
enable.md | No tools allowed |
plan |
enable.md | Read-only tools (Read, Glob, Grep) |
research |
enable.md | Read + web (WebFetch, WebSearch) |
monitor |
enable.md | Read + Bash |
off |
off.md | Disable AFK mode |
status |
status.md | Show current status |
review |
review.md | Review planning session |
| (empty/other) | enable.md | Default to full mode |
Usage Examples
/afk → full mode, default message
/afk full "In a meeting" → full mode, custom message
/afk plan "Explore codebase" → plan mode (read-only)
/afk research → research mode (read + web)
/afk off → disable
/afk status → check status
/afk review → review current/last session
/afk review 20240115_103000 → review specific session
State Management
All state operations use the script at scripts/state.sh:
"${CLAUDE_PLUGIN_ROOT}/skills/afk/scripts/state.sh" <command> [args]
Commands: enable, disable, is-enabled, get-state, get-mode, get-message, get-allowed, is-allowed, get-plan-path, get-log-path
What ships with it
5 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.
- 4d ago First seen · 55 lines · 46 tokens per session scan A 609e1bd7105b
afk is a skill published in the GitHub repository dhofheinz/open-plugins (9 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 549 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…