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/runtime-upgradegit 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.00019 | $0.05187 |
| Opus 5 | $0.00010 | $0.02593 |
| Sonnet 5 | $0.00004 | $0.01037 |
| Haiku 4.5 | $0.00002 | $0.00519 |
Grade A, and why
runtime-upgrade 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 3d 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 — 639 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runtime Dependency Upgrade
Strategic upgrade workflow for agent runtime dependencies. Unlike /app:upgrade (which treats all deps uniformly — "can we safely bump?"), this command performs deep changelog analysis, impact assessment, and feature discovery — "what should we build on top of the new version?"
When to Use This vs /app:upgrade
| Scenario | Use |
|---|---|
| Routine patch/minor bumps across all deps | /app:upgrade |
| Security-driven update to a runtime SDK | /app:upgrade |
| New major version of a runtime SDK with new features | /app:runtime-upgrade |
| Want to discover what new SDK capabilities to adopt | /app:runtime-upgrade |
Upgrading a dep that wraps our AgentRuntime interface |
/app:runtime-upgrade |
Arguments
Parse $ARGUMENTS for:
Required
<package-name>— The npm package to analyze. The three production runtime SDKs (all pre-configured in.claude/config/runtime-deps.json):@anthropic-ai/claude-agent-sdk,@openai/codex-sdk,@opencode-ai/sdk
Options
| Flag | Effect |
|---|---|
--to=<version> |
Target version (default: latest) |
--from=<version> |
Override current version detection |
Modes (mutually exclusive, default: interactive)
| Mode | Description |
|---|---|
analyze |
Fetch changelogs + produce impact assessment only (no specs) |
plan |
Analyze + generate specs for upgrade and feature adoption |
interactive |
Full guided workflow with decisions at each phase (default) |
Examples
/app:runtime-upgrade @anthropic-ai/claude-agent-sdk
/app:runtime-upgrade @anthropic-ai/claude-agent-sdk --to=0.3.0
/app:runtime-upgrade @openai/codex-sdk analyze
/app:runtime-upgrade @openai/codex-sdk plan --to=0.143.0
/app:runtime-upgrade @opencode-ai/sdk
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.
- 3d ago First seen · 639 lines · 19 tokens per session scan A 7c0dbdc5d79c
runtime-upgrade is a command published in the GitHub repository dork-labs/dorkos (9 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 5,187 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).
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.
feature
End-to-end authoring workflow for The Claude Code Bible — verify claims against the real tool, split chapters into path-disjoint slices, draft with parallel agents in this ONE checkout (never worktrees), fix TOC + cross-links, commit by path and merge. Reads intent from the prompt.
app-impact
Before merge, map every changed file to declared downstream consumers.
taskrunner-add
Add a task to the autonomous queue.