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/askgit clone --depth 1 https://github.com/dork-labs/dorkosWhat 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.00008 | $0.00496 |
| Opus 5 | $0.00004 | $0.00248 |
| Sonnet 5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
ask 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Help
Answer the question in $ARGUMENTS: how to accomplish a task in this repository, using Claude Code or manually.
Search order
Consult these sources, in order, until you can answer confidently:
.claude/README.md— complete harness inventory: every command, agent, skill, rule, and hook, plus naming conventions and maintenance guidesAGENTS.md— project architecture, conventions, quality standardsdecisions/— ADRs explaining why things are the way they are (usedecisions/manifest.jsonto find by topic)contributing/— 28 developer guides with detailed patterns (contributing/INDEX.mdmaps topics to guides).claude/rules/— path-specific rules (each haspaths:frontmatter declaring which files it governs)
Read the files the question actually touches — don't answer from memory when a source file can confirm.
Escalation
- Claude Code / Agent SDK / Claude API questions not answered by local docs: dispatch the
claude-code-guideagent — it has direct access to official documentation and is authoritative for hooks, skills, slash commands, MCP, settings, and SDK usage. - Non-Claude topics (libraries, general patterns): WebSearch.
When no process exists
If the repo has no defined process for the question, say so plainly, give best-effort guidance from similar patterns, then suggest the right follow-up:
/system:learn— when experimentation is needed to figure out the approach first/system:update— when the fix/process is already known and just needs codifying
Answer format
Give a direct answer with concrete file paths. When both exist, show both the Claude Code method (slash command, agent, or skill — prefer a slash command when one exists) and the manual method (the actual files/commands to touch). Note relevant caveats, e.g. /flow:* commands require the flow plugin (dork-labs/marketplace) loaded via --plugin-dir. Offer to execute the Claude Code method when that's clearly what the user wants.
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.
- 2d ago First seen · 38 lines · 8 tokens per session scan A d5f25e7d988f
ask is a command published in the GitHub repository dork-labs/dorkos (9 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 496 once invoked, about $0.0000 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 commands, from other repositories
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
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.
feature
End-to-end authoring workflow for The Claude Code Bible — verify claims against the real tool, split chapters into path-disjoint slices, draft with parallel agents in this ONE checkout (never worktrees), fix TOC + cross-links, commit by path and merge. Reads intent from the prompt.
app-impact
Before merge, map every changed file to declared downstream consumers.
taskrunner-add
Add a task to the autonomous queue.