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 skills/swingerman/engineer/post-mergenpx skills add swingerman/engineer --skill post-mergegit clone --depth 1 https://github.com/swingerman/engineerWhat 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.00068 | $0.01323 |
| Opus 5 | $0.00034 | $0.00661 |
| Sonnet 5 | $0.00014 | $0.00265 |
| Haiku 4.5 | $0.00007 | $0.00132 |
Grade A, and why
post-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 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
post-merge
The branch-hygiene skill that runs immediately after a PR merges — not deferred to the next session. next and session-summary already catch a stale branch at session boundaries (v1.7.1); post-merge closes the gap in between, where users were still asking "are we still on the feature branch?" mid-session.
When to use
- Auto — invoke right after observing a successful
gh pr merge,gh pr merge --auto, or a "Merged" PR state ingh pr view --json state. The agent that ran the merge calls this skill before doing anything else. - Manual —
/engineer.post-mergeor the trigger phrases above.
Not for: cleanup when the PR isn't merged yet (the work isn't done); session-end teardown (session-summary handles that); session-start survey (next already probes for stale branches as a backstop).
Workflow
-
Resolve + identify merged branch. Resolve the methodology root via
${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py. Get the current branch (git branch --show-current). If it'smain/master/the repo's default branch, there's nothing to clean — stop and report. -
Probe merge state. Run
git fetch origin --quiet, then check whether the current branch has been merged:- GitHub-side check (preferred when
ghis available):gh pr view --json state,mergedAt,headRefName --jq '.state'for the PR linked to this branch. State ofMERGEDis the strongest signal. - Git-side check (fallback):
git merge-base --is-ancestor HEAD origin/HEAD(ororigin/main). True means every commit on this branch is reachable from main.
If neither check confirms a merge, stop — the work isn't shipped yet. Report what was checked.
- GitHub-side check (preferred when
-
Run the cleanup. Run the three commands in order, stopping on any non-zero exit:
git checkout <default-branch> git pull --ff-only git branch -d <merged-branch>git branch -d(not-D) refuses unmerged work — non-destructive by construction. If it refuses, surface what's unmerged and stop; don't escalate to-Dwithout explicit user confirmation.
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 · 66 lines · 68 tokens per session scan A f69abc97593b
post-merge is a skill published in the GitHub repository swingerman/engineer (146 stars, last pushed 6d ago), licensed MIT. It adds 68 tokens to every session and 1,323 once invoked, about $0.0003 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 skills, from other repositories
writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.
release
Cut a sim-use release end-to-end. Use when the user runs /release or asks to "ship a release", "publish a version", "cut a release", or "release to homebrew". Drives scripts/local-release.sh; never reimplement its build/sign/tarball logic.
work-summary
Generates a project dashboard from MCP work items. Default is a lean, attention-first view: what's in flight, what's blocked, what to do next, what's queued. Use when the user says: project status, what's active, show me the dashboard, work summary, what should I work on, project health, what's blocked, where did I…
manage-schemas
Creates, views, edits, deletes, and validates note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Also recommends schema designs from a library of workflow patterns (autonomous coding loops, spec-driven teams…
bmad-dev-story
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan".
bmad-editorial-review-structure
Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure.