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 commands/dork-labs/dorkos/ongit clone --depth 1 https://github.com/dork-labs/dorkosWrote 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/commands/dork-labs/dorkos/on)<a href="https://agentmods.dev/commands/dork-labs/dorkos/on"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/on.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.00007 | $0.00697 |
| Opus 5 | $0.00003 | $0.00349 |
| Sonnet 5 | $0.00001 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade B, and why
on scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/settings.json 2>/dev/null || echo '{}' How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enable Notification Sound
Enable a sound notification when Claude finishes responding.
Step 1: Ask User for Scope
Use AskUserQuestion to determine where to enable notifications:
Question: "Where should notifications be enabled?"
Options:
- "User level (all projects)" - Applies to all Claude Code sessions
- "Project level (this project only)" - Only applies when working in this project
Step 2: Apply the Setting
User Level (~/.claude/settings.json)
If user selected "User level":
-
Read the current settings:
cat ~/.claude/settings.json 2>/dev/null || echo '{}' -
Check if Stop hook already exists. If not, add it.
-
Use a script to safely merge the Stop hook:
# Create the hook configuration node -e " const fs = require('fs'); const path = require('path'); const settingsPath = path.join(process.env.HOME, '.claude', 'settings.json'); let settings = {}; try { settings = JSON.parse(fs.readFileSync(settingsPath, 'utf8')); } catch (e) { settings = {}; } // Ensure hooks object exists if (!settings.hooks) settings.hooks = {}; // Add Stop hook with sound settings.hooks.Stop = [ { hooks: [ { type: 'command', command: 'afplay /System/Library/Sounds/Glass.aiff' } ] } ]; fs.writeFileSync(settingsPath, JSON.stringify(settings, null, 2)); console.log('Notification sound enabled at user level (~/.claude/settings.json)'); "
Project Level (.claude/settings.json)
If user selected "Project level":
-
Read the current project settings:
cat .claude/settings.json 2>/dev/null || echo '{}' -
Use a script to safely merge the Stop hook:
node -e " const fs = require('fs'); const settingsPath = '.claude/settings.json'; let settings = {}; try { settings = JSON.parse(fs.readFileSync(settingsPath, 'utf8')); } catch (e) { settings = {}; } // Ensure hooks object exists if (!settings.hooks) settings.hooks = {}; // Add Stop hook with sound settings.hooks.Stop = [ { hooks: [ { type: 'command', command: 'afplay /System/Library/Sounds/Glass.aiff' } ] } ]; fs.writeFileSync(settingsPath, JSON.stringify(settings, null, 2)); console.log('Notification sound enabled at project level (.claude/settings.json)'); "
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 · 132 lines · 7 tokens per session scan B 773660917b7e
on is a command published in the GitHub repository dork-labs/dorkos (9 stars, last pushed 3d ago), licensed MIT. It adds 7 tokens to every session and 697 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
tidy
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.
swarm-planner
Generates a structured execution plan with dependency tracking using the Swarms-inspired planning methodology.
review-queue
Display and manage the human review queue for parallel autonomous operations.
nio
Nio — scan code, evaluate an action, read the audit report, manage config.
taskrunner-add
Add a task to the autonomous queue.
scout-setup
First-time install of Scout. Detects connected tools, collects user details, and hands off to scoutctl bootstrap install. For upgrading an existing vault, run /scout-update.