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/statusgit 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/status)<a href="https://agentmods.dev/commands/dork-labs/dorkos/status"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/status.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.00009 | $0.00567 |
| Opus 5 | $0.00005 | $0.00283 |
| Sonnet 5 | $0.00002 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade B, and why
status 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
if grep -q "afplay" ~/.claude/settings.json 2>/dev/null; then What it actually says
Notification Sound Status
Check the notification sound configuration at both user and project levels.
Check Status
Run the following to check both levels:
echo "╔══════════════════════════════════════════════════════════════╗"
echo "║ Notification Sound Status ║"
echo "╠══════════════════════════════════════════════════════════════╣"
# Check user level
echo "║"
echo "║ User Level (~/.claude/settings.json)"
if [ -f ~/.claude/settings.json ]; then
if grep -q "afplay" ~/.claude/settings.json 2>/dev/null; then
echo "║ Status: ✓ ENABLED"
# Extract the sound file being used
SOUND=$(grep -o 'afplay [^"]*' ~/.claude/settings.json 2>/dev/null | head -1 | sed 's/afplay //')
echo "║ Sound: $SOUND"
else
echo "║ Status: ✗ DISABLED"
fi
else
echo "║ Status: ✗ DISABLED (no settings file)"
fi
echo "║"
echo "╠══════════════════════════════════════════════════════════════╣"
echo "║"
# Check project level
echo "║ Project Level (.claude/settings.json)"
if [ -f .claude/settings.json ]; then
if grep -q "afplay" .claude/settings.json 2>/dev/null; then
echo "║ Status: ✓ ENABLED"
# Extract the sound file being used
SOUND=$(grep -o 'afplay [^"]*' .claude/settings.json 2>/dev/null | head -1 | sed 's/afplay //')
echo "║ Sound: $SOUND"
else
echo "║ Status: ✗ DISABLED"
fi
else
echo "║ Status: ✗ DISABLED (no settings file)"
fi
echo "║"
echo "╠══════════════════════════════════════════════════════════════╣"
echo "║"
echo "║ Commands:"
echo "║ /cc:notify:on - Enable notification sound"
echo "║ /cc:notify:off - Disable notification sound"
echo "║"
echo "╚══════════════════════════════════════════════════════════════╝"
Notes
- User level applies to all Claude Code sessions
- Project level applies only to this project
- Project-level settings override user-level settings
- Restart Claude Code after changes for them to take effect
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 · 70 lines · 9 tokens per session scan B 72ee6c50d13e
status is a command published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 567 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.
taskrunner-add
Add a task to the autonomous queue.
single-cli
ORCHESTRATOR. Run the autonomy loop as subagents in ONE terminal (coordination.mode=single-cli; default OFF; fail-closed). Re-runs decideCoordination, refuses if no independent verification remains, then drives a sequential builder/reviewer baton where the deterministic gate BINDS and the LLM critique is ADVISORY.
ocean-stop
Gracefully stop the boil-ocean run and its scheduler.