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.
git 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/triage)<a href="https://agentmods.dev/commands/dork-labs/dorkos/triage"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/triage/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/triage"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/triage.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.00028 | $0.05838 |
| Opus 5.5 | $0.00011 | $0.02335 |
| Sonnet 5.5 | $0.00006 | $0.01168 |
| Haiku 4.5 | $0.00003 | $0.00584 |
Grade A, and why
triage scanned grade A 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 24d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Read, Bash(composio:*), Bash(gh:*), Bash(curl:*), Bash(python3:*), Bash(node:*), AskUserQuestion How it starts
The opening of the file, as written. The whole thing — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process the User-Feedback Queue
Argument: $ARGUMENTS
Purpose
User bug reports and ideas land as Linear issues in the DorkOS User Feedback
(FB) team's Triage. Nothing works that queue automatically — this command is
the whole processing loop. It has two modes with deliberately different safety
profiles:
- Default (no argument): triage + anomaly report. Safe to run any time. Every write it makes is silent to reporters and reversible.
--sweep: the shipped-email pass. Its ONLY sanctioned trigger is the release flow (/system:releaseinvokes it). A DOR issue goes Done at merge; the reporter's fix is only real at release. Running the sweep at any other moment tells a named human "this shipped" about work they cannot get yet. Do not run--sweepad hoc.
Both modes serve one promise, meta/user-care.md: a person who reports
something hears back within one business day (heard), hears what we decided
within five (decided), and hears when it ships (shipped). Nobody gets
silence. Reports arrive through two doors. The in-app "Send feedback" dialog
files into FB directly. GitHub issues on dork-labs/dorkos are mirrored in by
step 0 below. The door decides where each reply goes, never whether it happens.
How to word a reply is the writing-to-users skill.
A business day here is Monday to Friday in the operator's local time. Weekends do not count toward the one-day and five-day deadlines. Every other duration in this file is plain calendar time and says so.
If meta/user-care.md or the writing-to-users skill is missing from this
checkout, stop and say which one. They are the standard and the wording rules
for every reply below. Never draft a reply to a named person freehand because a
file did not resolve; a form letter to somebody who took the time to write to us
is worse than being an hour late.
Ground rules that protect reporters (from the process design debate,
2026-09-11; ops context in contributing/feedback-pipeline-ops.md):
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.
- 24d ago Changed · +316 lines 8e065be6d33f
- 27d ago First seen · 128 lines · 28 tokens per session scan A 9fd3cfed5634
triage is a command published in the GitHub repository dork-labs/dorkos (10 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 5,838 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-12.
Other commands, from other repositories
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
scout-work
Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).
scout-work
Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).
modernize-preflight
Run this first — checks the environment, records where the code lives, and says what to fix before anything else runs.
sp.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.