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 agentmods add commands/dork-labs/dorkos/typesgit clone --depth 1 https://github.com/dork-labs/dorkosWhat 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 | $0.00013 | $0.00752 |
| Opus 5 | $0.00006 | $0.00376 |
| Sonnet 5 | $0.00003 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
types 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 2d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Type Error Debugging
Debug and fix the TypeScript error(s) described by $ARGUMENTS (an error message, a file path, or empty for a full typecheck). Load the debugging-typescript-errors skill — it carries the methodology (trace the real mismatch, minimal verified fix, explain the underlying concept). This command adds the project-specific ground truth below.
Running typecheck in this repo
pnpm typecheck # All packages via Turborepo (~28s)
pnpm --filter @dorkos/server typecheck # One package (~4s) — prefer for the fix loop
pnpm --filter @dorkos/client typecheck
Gotcha: after pulling, a stale @dorkos/shared dist causes false-red errors in downstream packages (imports resolve to old types). Rebuild first: pnpm --filter @dorkos/shared build. If errors reference @dorkos/shared exports that clearly exist in packages/shared/src/, this is almost certainly the cause.
Project-specific type landscape
- Zod is the type source of truth for runtime data: schemas in
packages/shared/src/schemas.ts,relay-schemas.ts,mesh-schemas.ts,config-schema.ts; derive withz.infer<typeof Schema>rather than hand-writing parallel interfaces. - Database types come from Drizzle — schemas in
packages/db(SQLite). Use Drizzle's inferred types ($inferSelect/$inferInsert), not manual assertions. - Cross-package imports use
@dorkos/shared/*subpaths (/types,/agent-runtime,/transport, ...). "Cannot find module" on these usually means a stale dist (see gotcha) or a missing subpath inpackages/shared/package.jsonexports. - Server is NodeNext — relative imports in
apps/serverneed explicit.jsextensions; TS2307 there is often a missing extension, not a missing file. - Client hooks are typed TanStack Query wrappers in
apps/client/src/layers/entities/*/model/; Express routes validate bodies withSchema.safeParse(req.body)(Express 5:req.bodycan be undefined on empty POSTs). anyis banned (project rule) — fix the type, don't silence it. Prefer type guards over assertions.
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.
- 2d ago First seen · 41 lines · 13 tokens per session scan A 0310b7e2dc9b
types is a command published in the GitHub repository dork-labs/dorkos (9 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 752 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
tidy
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.
swarm-planner
Generates a structured execution plan with dependency tracking using the Swarms-inspired planning methodology.
review-queue
Display and manage the human review queue for parallel autonomous operations.
taskrunner-add
Add a task to the autonomous queue.
single-cli
ORCHESTRATOR. Run the autonomy loop as subagents in ONE terminal (coordination.mode=single-cli; default OFF; fail-closed). Re-runs decideCoordination, refuses if no independent verification remains, then drives a sequential builder/reviewer baton where the deterministic gate BINDS and the LLM critique is ADVISORY.