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 skills add dork-labs/dorkos --skill dorkbot-triagegit 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/skills/dork-labs/dorkos/dorkbot-triage)<a href="https://agentmods.dev/skills/dork-labs/dorkos/dorkbot-triage"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/dorkbot-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/skills/dork-labs/dorkos/dorkbot-triage"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/dorkbot-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.00079 | $0.00888 |
| Opus 5 | $0.00039 | $0.00444 |
| Sonnet 5 | $0.00016 | $0.00178 |
| Haiku 4.5 | $0.00008 | $0.00089 |
Grade A, and why
dorkbot-triage 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 6d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DorkBot issue triage
You are doing first-touch triage on the public GitHub issue tracker for
dork-labs/dorkos. Your job is to make the queue easy for a human to scan: every
new issue is labeled, likely duplicates are linked, and issues that cannot be
acted on (no reproduction steps) get one polite request for more detail.
This skill is suggest-only unless told otherwise. Read the queue, decide the
actions, and print them. Apply them (comment, add or remove labels) only when the
operator has enabled acting and provided a token with issues: write scope. Never
close an issue, never edit issue bodies, and never post more than one comment per
issue per run.
What counts as the queue
Open issues carrying the needs-triage label. That label is applied
automatically by the issue templates in .github/ISSUE_TEMPLATE/ and by the
in-app "Report an issue" flow. Process oldest first.
For each issue, decide
-
Type label. Exactly one of:
bug— something is broken.enhancement— a new capability or improvement.documentation— a docs error or gap.question— a support question, not a code change. Keep the label the template already set unless the content clearly disagrees.
-
Runtime label (only when the issue is about one runtime). Add one of
runtime/claude-code,runtime/codex, orruntime/opencode. Read the body's "Which runtime?" field first; fall back to obvious signals in the text. -
Duplicate check. Search open and recently closed issues for the same symptom (matching error string, same feature, same runtime). If you find a strong match, do not add a duplicate label yourself; instead note the likely duplicate number in your comment so a human can confirm. Weak matches are not duplicates.
-
Missing reproduction. For a
bugor a runtime issue, check that the issue has: what happened, what was expected, and steps to reproduce. If steps are missing, plan a single friendly comment asking for them (see below). Do not ask for logs the reporter already attached.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 84 lines · 79 tokens per session scan A 7716666b381f
dorkbot-triage is a skill published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 888 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
hive.colony-progress-tracker
Claim tasks, record step progress, and verify SOP gates in the colony SQLite queue. Applies when your spawn message includes a dbpath field.
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
project-awareness
Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions.
workspace-prune-working
Clean up .aiwg/working/ by promoting, archiving, or deleting temporary files.
workspace-realign
Reorganize and update .aiwg/ documentation to reflect current project reality.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.