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/logsWrote 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/logs)<a href="https://agentmods.dev/commands/dork-labs/dorkos/logs"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/logs/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/logs"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/logs.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.00012 | $0.03631 |
| Opus 5.5 | $0.00005 | $0.01452 |
| Sonnet 5.5 | $0.00002 | $0.00726 |
| Haiku 4.5 | $0.00001 | $0.00363 |
Grade A, and why
logs 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 1mo 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 — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Server Log Analysis
Systematically analyze server logs from the .dork/logs/ directory to diagnose errors, exceptions, API failures, and unexpected behavior. DorkOS uses NDJSON structured logging — each line is a JSON object that can be filtered with jq.
Read
contributing/observability.mdfirst. It is the reference for what the log contains and how to read it: the field list, the level table, the refusal rule (reason+visibility), the tag registry, and a worked end-to-end walkthrough of a room incident.
dispatchIdis the first filter to reach for. Onedsp_<ULID>joins every hop of one message's life — the room entry, the claim, the turn, the reply, the relay delivery — sojq -c 'select(.dispatchId=="dsp_…")' "$L"reconstructs a single exchange in order instead of guessing from timestamps. Start there, then widen. When the server is still running,dorkos debug dispatchesanddorkos debug refusalsanswer what the log cannot, because the state is only in memory.
Log System Overview
- Format: NDJSON (newline-delimited JSON)
- Active log:
{DORK_HOME}/logs/dorkos.log - Rotation: Daily (
dorkos.YYYY-MM-DD.log) + size-based within a day (dorkos.YYYY-MM-DD.N.log) - Fields:
level,time,msg,tag(optional), plus arbitrary context fields - Levels:
fatal(60),error(50),warn(40),info(30),debug(20),trace(10)
DORK_HOME Location
The .dork directory location depends on the environment:
| Environment | Location | How |
|---|---|---|
| Development | apps/server/.temp/.dork/ |
Auto-detected when NODE_ENV !== 'production' |
| Production (CLI) | ~/.dork/ |
Default, or DORK_HOME env var |
| Custom | Any path | Set DORK_HOME env var |
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.
- 1mo ago First seen · 383 lines · 12 tokens per session scan A 850af5177d9b
logs is a command published in the GitHub repository dork-labs/dorkos (12 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 3,631 once invoked, about $0.0000 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}}.
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.
doctor
Diagnose a broken llm-router setup.
relationships
Explore dependencies and relationships for a file or code pattern.