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/marcusquinn/aidevops/launch-workergit clone --depth 1 https://github.com/marcusquinn/aidevopsWhat 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.00014 | $0.00621 |
| Opus 5 | $0.00007 | $0.00311 |
| Sonnet 5 | $0.00003 | $0.00124 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
launch-worker 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Args: $ARGUMENTS — <issue|issue,issue> [owner/repo] [--model <id>] [--agent <name>] [--batch <list>] [--dry-run]
owner/repo is optional. When omitted, aidevops launch-worker resolves the
current git repository from origin and dispatches against that repo.
What this does
Runs the first-class manual worker launcher:
aidevops launch-worker $ARGUMENTS
Use it when an operator needs to start workers intentionally instead of waiting for the next pulse cycle: smoke-testing a new issue, retrying after fixing a dispatch blocker, or launching a controlled batch with a specific model.
Syntax
# Preview one dispatch without launching, using the current git repo
aidevops launch-worker 22259 --dry-run
# Preview one dispatch without launching, using an explicit repo
aidevops launch-worker 22259 marcusquinn/aidevops --dry-run
# Launch one issue with default agent Build+ in the current repo
aidevops launch-worker 22259
# Launch multiple issues in the current repo with repeated issue arguments
aidevops launch-worker 22259 22260 22261
# Batch launch multiple issues in the current repo
aidevops launch-worker --batch 22259,22260 --dry-run
# Force a model and agent
aidevops launch-worker 22259 marcusquinn/aidevops \
--model anthropic/claude-opus-4-7 --agent Build+
# Batch launch against an explicit repo
aidevops launch-worker --batch 22259,22260 marcusquinn/aidevops --dry-run
# Status for the current repo
aidevops launch-worker status 22259
Safety expectations
The launcher delegates to dispatch-single-issue-helper.sh dispatch, preserving
the manual-dispatch ceremony: issue must be open, parent tasks are blocked,
dedup is checked fail-closed, status moves to status:queued, origin:worker
is applied, the runner is assigned, a worktree is created from origin/<default>,
and the dispatch ledger is registered.
Output
Successful real launches print:
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 · 81 lines · 14 tokens per session scan A 2b2ef7ba564f
launch-worker is a command published in the GitHub repository marcusquinn/aidevops (391 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 621 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-30.
Other commands, from other repositories
ccasp-setup.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
gsd:new-milestone
Start a new milestone cycle — update PROJECT.md and route to requirements.
gsd:execute-phase
Execute all plans in a phase with wave-based parallelization.
gsd:audit-milestone
Audit milestone completion against original intent before archiving.
gsd:progress
Check project progress, show context, and route to next action (execute or plan).
gsd:insert-phase
Insert urgent work as decimal phase (e.g., 72.1) between existing phases.