Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dork-labs/dorkosnpx agentmods add commands/dork-labs/dorkos/apiWrote 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/api)<a href="https://agentmods.dev/commands/dork-labs/dorkos/api"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/api/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/dork-labs/dorkos/api"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/api.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00025 | $0.03231 |
| Opus 5.5 | $0.00010 | $0.01292 |
| Sonnet 5.5 | $0.00005 | $0.00646 |
| Haiku 4.5 | $0.00003 | $0.00323 |
Grade A, and why
api 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.
How it starts
The opening of the file, as written. The whole thing — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API & Data Flow Debugging
Debug data-related issues by systematically tracing through the project's data flow layers. This command helps with API failures, data mismatches, stale cache, and service errors.
For anything on the messaging path — a room, a session turn, a task run, a chat integration — read
contributing/observability.mdand start fromdispatchId. Onedsp_<ULID>joins every hop of one message's life, sojq -c 'select(.dispatchId=="dsp_…")'gives you the whole chain in order rather than a layer at a time. If the server is still up,dorkos debug session <id>answers what is only in memory: the lifecycle, the write lock, and what the turn is parked on.
Project Data Flow Architecture
+-------------------+
| React Component | <- UI displays data (FSD layers)
+-------------------+
| TanStack Query | <- Client-side caching & fetching
+-------------------+
| Transport Layer | <- HttpTransport (HTTP and durable streams)
+-------------------+
| Hono Route | <- HTTP endpoints (Zod validation, boundary checks)
+-------------------+
| Service Layer | <- Business logic (agent-manager, binding-router, etc.)
+-------------------+
| Data Store | <- SQLite (dork.db) + JSONL transcripts + JSON state files
+-------------------+
Key Differences from Typical Projects
- SQLite, not PostgreSQL — Drizzle ORM (
packages/db) over SQLite (WAL mode), plus JSON state files - No server actions — All mutations go through the server's REST endpoints (Hono)
- Transport abstraction — Client uses
Transportinterface, not direct fetch - SDK transcripts — Sessions are derived from JSONL files on disk, not a database
- Feature-flag guarded — Relay/Mesh/Pulse endpoints return 503 when disabled
Arguments
Parse $ARGUMENTS:
- If
--url <url>flag provided, navigate to that URL - Remaining text describes the endpoint or feature with issues
- If empty, prompt for details
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 Changed · +2 lines · +1 tokens per session 415167759f7c
- 21d ago Changed a784b96d34a1
- 1mo ago First seen · 366 lines · 24 tokens per session scan A 3a5035dfe743
api is a command published in the GitHub repository dork-labs/dorkos (10 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 3,231 once invoked, about $0.0001 per session on Opus 5.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
debug-issue
I'm experiencing the following issue: {{1}}.
dev-error-handling
Implements a robust and consistent error handling strategy.
railroad
Specialized debugging for Railway-hosted backend issues: deployment failures, API errors, database problems, and environment configuration.
verify-architecture
Run 64 HOR rules and structural verification on the current codebase.
build-fix
Incrementally fix TypeScript and build errors with minimal diffs. Fix one error at a time for safety.
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.