Borrowing it
Nothing to install: this file belongs to dork-labs/dorkos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dork-labs/dorkos/main/AGENTS.mdgit 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/instructions/dork-labs/dorkos/agents-md)<a href="https://agentmods.dev/instructions/dork-labs/dorkos/agents-md"><img src="https://agentmods.dev/badge/instructions/dork-labs/dorkos/agents-md.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.1 | $0.08227 | $0.08227 |
| Opus 5 | $0.04113 | $0.04113 |
| Sonnet 5 | $0.01645 | $0.01645 |
| Haiku 4.5 | $0.00823 | $0.00823 |
Grade A, and why
dorkos AGENTS.md 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 today.
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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Vision
DorkOS is the operating system for autonomous AI agents — the coordination layer (scheduling, communication, discovery, memory) that lets one person ship like a team. Core thesis: intelligence doesn't scale; coordination does. Market entry point (2026-07, language settled 2026-08 by DOR-1517): one place for every AI agent you run — running Claude Code, Codex, and OpenCode side by side in one window is the headline differentiator. Current strategy lives in meta/positioning-202607/00-overview.md. Full vision: meta/dorkos-litepaper.md; brand: meta/brand-foundation.md; personas: meta/personas/ (Kai — senior dev running 10 agents across 5 projects, dismisses chatbot wrappers; Priya — staff architect in Obsidian, reads source before adopting; Ikechi — non-developer founder shipping apps by directing agents; Lil — privacy-first non-technical professional, horizon-staged, not a launch target; the anti-persona is whoever won't operate their own system — operator mentality, not technical skill, is the line). Tagline (2026-07-09): "You, Multiplied." on hero surfaces; "Intelligence doesn't scale. Coordination does." is the manifesto line for essays and anti-positioning only.
Never write "mission control" or "cockpit" in user-facing prose (site, docs, READMEs, UI copy, error messages, release notes) — the operator retired both words, and the category phrase is "one place" ("All your agents. One place." / "one place for every AI agent you run"). Say "the DorkOS app", "the app", "one place" or "one window" instead. Two carve-outs: GitHub ships a product literally named "Mission Control", and the compiled changelog keeps its historical wording. Enforced by scripts/check-banned-words.sh in the typecheck workflow, which scans this file too. This paragraph is deliberately its own paragraph: the guard matches line by line, so the marker below exempts exactly the prose that has to name the two retired words and nothing else in the file.
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.
- today Changed · +7 lines · +482 tokens per session 20794a42a68a
- yesterday Changed · +124 tokens per session b9f28a5f7fc5
- 3d ago First seen · 191 lines · 7,621 tokens per session scan A 3d8765d9319e
dorkos AGENTS.md is an instructions file published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), licensed MIT. It adds 8,227 tokens to every session, about $0.0411 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.