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/spillwavesolutions/wiki_ticket_sdd/mergegit clone --depth 1 https://github.com/SpillwaveSolutions/wiki_ticket_sddWrote 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/spillwavesolutions/wiki_ticket_sdd/merge)<a href="https://agentmods.dev/commands/spillwavesolutions/wiki_ticket_sdd/merge"><img src="https://agentmods.dev/badge/commands/spillwavesolutions/wiki_ticket_sdd/merge.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.00514 |
| Opus 5 | $0.00014 | $0.00257 |
| Sonnet 5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
merge 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 5d 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.
What it actually says
/worklog:merge
Merging with red or pending gates is never an option; this command encodes the house rule. Never squash (ADR-0008).
-
Confirm the PR number with the user if not given.
-
Run, in the background so the session stays free:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/merge-when-green.sh" <pr>Defaults: 60 s × 120 (2 h). The script arms
gh pr merge --auto --mergeimmediately; the poll is fallback. Exit meanings: 0 merged · 1 failing checks, NOT merged · 2 no gh CLI · 3 PR not open · 4 timed out waiting. -
On merge: pull the base branch and delete the local feature branch. Roadmap/index regeneration and
worklog sync --reportrun inworklog-post-mergeon main — do not wait on them. Run ticket-sync locally only if closed items still need a push the report did not cover. -
On failure or timeout: report the failing checks; fixing them is the path to merging — never
--admin, never bypass, never--squash.
Auto-merge flag
features.auto_merge_on_green in .work/config.yml (default true)
decides what happens when gates go green: true merges; false is advisory
mode — the script reports green, does NOT merge, and waits for a human to
run gh pr merge <pr> --merge. Overrides, strongest first: --auto /
--advisory as first argument to the script (one run only), then
WORKLOG_AUTO_MERGE=1|0 in the environment, then the config value.
Red/pending/timeout behavior is identical in both modes.
--auto queues server-side only when the host repo allows auto-merge and
required checks exist on the base branch (ADR-0010). Otherwise the poll
loop merges once green.
Non-GitHub platforms: same rule, their CLI (glab mr merge --when-pipeline-succeeds,
az repos pr update --auto-complete) — prefer the platform's native
merge-when-green if it has one.
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.
- 5d ago First seen · 43 lines · 27 tokens per session scan A 83ab4a515fcb
merge is a command published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (10 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 514 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.