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/resetgit 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.00006 | $0.00537 |
| Opus 5 | $0.00003 | $0.00269 |
| Sonnet 5 | $0.00001 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
reset 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reset VS Code IDE Color Scheme
Remove the custom workbench.colorCustomizations from .vscode/settings.json, restoring VS Code to its default theme colors.
Scope
IMPORTANT: This command ONLY modifies project-level settings.
| Setting | Path | Modified? |
|---|---|---|
| Project settings | .vscode/settings.json |
YES |
| User settings | ~/.config/Code/User/settings.json |
NEVER |
| User settings (macOS) | ~/Library/Application Support/Code/User/settings.json |
NEVER |
NEVER read, write, or modify any file outside the project's .vscode/ directory.
Steps
Step 1: Read Project Settings
Read .vscode/settings.json (project-level ONLY) to check if custom colors exist.
If the file doesn't exist, inform the user there's nothing to reset.
CRITICAL: Do NOT read or check any user-level VS Code settings files.
Step 2: Check for Custom Colors
Look for the workbench.colorCustomizations key in the settings object.
If it doesn't exist or is empty, inform the user there's no custom color scheme to remove.
Step 3: Remove Color Customizations
If workbench.colorCustomizations exists:
- Remove the entire
workbench.colorCustomizationskey and its contents - Preserve ALL other settings in the file (e.g.,
terminal.integrated.tabs.title, editor settings, etc.) - Write the updated settings back to the file with proper JSON formatting
Step 4: Handle Empty Settings
If removing workbench.colorCustomizations leaves only {}, keep the file with the empty object rather than deleting it.
Output
If colors were removed:
IDE Theme Reset
Status: Custom colors removed
File: .vscode/settings.json
VS Code will now use its default theme colors.
Restart VS Code if the change doesn't take effect immediately.
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 · 86 lines · 6 tokens per session scan A a044a64fde40
reset is a command published in the GitHub repository dork-labs/dorkos (9 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 537 once invoked, about $0.0000 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.