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/lugassawan/swe-workbench/documentgit clone --depth 1 https://github.com/lugassawan/swe-workbenchWhat 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.00024 | $0.00451 |
| Opus 5 | $0.00012 | $0.00226 |
| Sonnet 5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
document 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 yesterday.
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.
What it actually says
Target: $ARGUMENTS
If $ARGUMENTS contains a ticket reference, invoke swe-workbench:ticket-context first and prepend its structured summary to the delegation context below. Skip if $ARGUMENTS is free-text with no recognizable ref. (Trigger patterns are defined in that skill's "When to invoke" section.)
Delegate to the swe-workbench:tech-writer subagent. Its output must include:
- Artifact type — which category (README section, ADR, ARCHITECTURE/OVERVIEW, inline comment).
- Target path — the exact file path the artifact will live at.
- Style notes detected — heading case, voice, list style, em-dash usage, and any other conventions observed in existing top-level docs.
- Draft or diff — the content to be written.
- Citations — commit hash or file:line for every factual claim in committed artifacts; conversation excerpt is acceptable only in drafts.
Absolute rule: never invent behavior. If the diff doesn't show it, don't document it.
Plan output: If you (the orchestrator) author a plan based on the subagent's response and that plan modifies the codebase (fix / make / implement) — whether saved to a plan file or passed to ExitPlanMode — first activate swe-workbench:workflow-development in Mode A and embed the rendered ## Workflow section in the plan per skills/workflow-development/templates/plan-workflow-section.md. Run the skill's project-detection (git branch -a, git log --oneline -20, Makefile grep, PR-template lookup) so the placeholders are substituted from this repo, not left as [[detect:…]]. Skip Mode A if the plan is pure analysis, design recommendation, or any output that does not introduce file edits — the Workflow section's phases (Branch / Verify / Deliver) do not apply.
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.
- yesterday First seen · 21 lines · 24 tokens per session scan A b3fdfa871f63
document is a command published in the GitHub repository lugassawan/swe-workbench (2 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 451 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
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
release-tag
Create and push a version tag after a release PR has been merged.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
deploy
Build, test, deploy with staged rollout.
simplify
Reduce complexity without changing behavior — code simplification.
gum-schema
Print a JSON description of the active gum command tree, including command paths, aliases, arguments, and flags.