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.
git clone --depth 1 https://github.com/derek-larson14/delegateWrote 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/commands/derek-larson14/delegate/update)<a href="https://agentmods.dev/commands/derek-larson14/delegate/update"><img src="https://agentmods.dev/badge/commands/derek-larson14/delegate/update/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/commands/derek-larson14/delegate/update"><img src="https://agentmods.dev/badge/commands/derek-larson14/delegate/update.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.00008 | $0.01423 |
| Opus 5.5 | $0.00003 | $0.00569 |
| Sonnet 5.5 | $0.00002 | $0.00285 |
| Haiku 4.5 | $0.00001 | $0.00142 |
Grade C, and why
update scanned grade C with 2 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/delegate-update /tmp/delegate-update.zip Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
mkdir -p ops/scripts && curl -sL https://raw.githubusercontent.com/derek-larson14/delegate/main/ops/scripts/check-updates.sh -o ops/scripts/check-updates.sh && chmod +x ops/scripts/check-updates.sh && ops/scripts/check-u How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Commands
Download the latest commands and scripts from the delegate repo.
Steps
0. Detect OS
uname -s 2>/dev/null || echo "Windows"
If the output contains "MINGW", "CYGWIN", "MSYS", or "Windows", this is a Windows environment. Use PowerShell (.ps1) scripts and $env:TEMP paths throughout. Otherwise, use bash (.sh) scripts and /tmp/ paths (existing behavior).
1. Run the update checker
macOS/Linux:
If ops/scripts/check-updates.sh exists, run it:
ops/scripts/check-updates.sh
If it doesn't exist, bootstrap it first:
mkdir -p ops/scripts && curl -sL https://raw.githubusercontent.com/derek-larson14/delegate/main/ops/scripts/check-updates.sh -o ops/scripts/check-updates.sh && chmod +x ops/scripts/check-updates.sh && ops/scripts/check-updates.sh
Windows:
If ops/scripts/check-updates.ps1 exists, run it:
powershell.exe -ExecutionPolicy Bypass -File ops/scripts/check-updates.ps1
If it doesn't exist, bootstrap it first:
powershell.exe -ExecutionPolicy Bypass -Command "New-Item -ItemType Directory -Path ops/scripts -Force | Out-Null; Invoke-WebRequest -Uri 'https://raw.githubusercontent.com/derek-larson14/delegate/main/ops/scripts/check-updates.ps1' -OutFile 'ops/scripts/check-updates.ps1' -UseBasicParsing; & './ops/scripts/check-updates.ps1'"
If the script says "Everything is up to date" — you're done, skip to cleanup.
If no CHANGED/NEW/LOCAL ONLY items appear, everything is up to date - skip to cleanup.
LOCAL ONLY items exist locally but not upstream - either custom local files or deleted from repo. Mention these in the summary.
2. Review command changes
For CHANGED files: Show the diff to understand what changed.
macOS/Linux:
diff -u ".claude/commands/<name>" "/tmp/delegate-update/delegate-main/.claude/commands/<name>"
Windows — use the extracted path under $env:TEMP:
powershell.exe -Command "Compare-Object (Get-Content '.claude/commands/<name>') (Get-Content (Join-Path $env:TEMP 'delegate-update/delegate-main/.claude/commands/<name>'))"
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.
- 1mo ago First seen · 169 lines · 8 tokens per session scan C 8b807c823276
update is a command published in the GitHub repository derek-larson14/delegate (39 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 1,423 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.