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/listgit 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/list)<a href="https://agentmods.dev/commands/dork-labs/dorkos/list"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/list.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.00288 |
| Opus 5 | $0.00005 | $0.00144 |
| Sonnet 5 | $0.00002 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
list 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 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.
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
List Architecture Decision Records
Steps
Step 1: Read Manifest
Read decisions/manifest.json to get all decision entries.
Step 2: Display Main Table
Format and display all ADRs as a markdown table, sorted by id:
## Architecture Decision Records
| # | Title | Status | Date | Spec |
| ---- | ------------------------------- | -------- | ---------- | --------------------- |
| 0001 | [Title](decisions/0001-slug.md) | accepted | 2026-02-06 | claude-code-webui-api |
| 0002 | [Title](decisions/0002-slug.md) | accepted | 2026-02-15 | fsd-architecture |
Step 3: Display Summary
Total: N decisions (A accepted, P proposed, X deprecated, S superseded)
If the proposed count is large, suggest /adr:review to progress the backlog.
Notes
- Sort by id (legacy 4-digit numbers sort before timestamp ids under a plain string sort — that's chronological)
- Link titles to the actual files
- Show spec slug if linked, "—" if not
- Status uses lowercase
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 · 42 lines · 9 tokens per session scan A ad14f05e04f9
list 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 288 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
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
plan-regression-tests
Plan regression tests for existing code with it.skip statements.
ado-pull
Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
github-push
Push local progress to GitHub Issues (like git push). Updates issue with task completion checklist.
harness-adopt
Apply Harness Starter Kit to the current target repository with the prompt-first adoption workflow.
swarm-planner
Generates a structured execution plan with dependency tracking using the Swarms-inspired planning methodology.