Borrowing it
Nothing to install: this file belongs to SAGAAIDEV/mcp-ahrefs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SAGAAIDEV/mcp-ahrefs/main/.claude/commands/post-merge.mdgit clone --depth 1 https://github.com/SAGAAIDEV/mcp-ahrefsWrote 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/sagaaidev/mcp-ahrefs/post-merge)<a href="https://agentmods.dev/commands/sagaaidev/mcp-ahrefs/post-merge"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/post-merge/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/sagaaidev/mcp-ahrefs/post-merge"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/post-merge.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.00015 | $0.00455 |
| Opus 5.5 | $0.00006 | $0.00182 |
| Sonnet 5.5 | $0.00003 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
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 2mo 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
I'll help you complete the post-merge workflow to ensure your local environment is synchronized and the merged changes are validated.
Step 1: Sync with Remote Main
Switching to main and pulling latest changes:
!git checkout main !git pull origin main
Verifying your changes are included: !git log --oneline -5
Step 2: Re-run Feature Tests
Re-running the same tests that validated your feature:
!pytest !ruff check .
Step 3: Clean Up Branch
Getting the previous branch name and deleting it:
!git branch -d $(git rev-parse --abbrev-ref @{-1})
Cleaning up remote tracking branches: !git remote prune origin
Step 4: Update Development Environment
Ensuring dependencies are up to date:
!pip install -e ".[dev]"
Step 5: Verify Everything Works
Running a final check to ensure the development environment is healthy:
!python -c "import conduit; print('Conduit package imported successfully')" !pytest --collect-only | head -20
Summary
Post-merge actions completed! Your local environment is now:
- Synchronized with the latest main branch
- All tests passing
- Issue branch cleaned up
- Dependencies updated
You're ready to start your next issue!
🚀 Next Steps
Now that your issue is merged and environment is clean:
-
Start a new issue:
/project:start-issue [ISSUE-KEY] [SITE-ALIAS]Begin work on your next JIRA issue (feature, bug, or task)
-
List available sites:
/project:list-sitesIf you need to check which Atlassian sites are configured
-
Check JIRA board:
- Review your team's backlog
- Pick up the next priority issue
- Coordinate with your team on Slack/Teams
💡 Tip: Your development environment is fresh and ready for the next issue!
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.
- 2mo ago First seen · 75 lines · 15 tokens per session scan A 9edd1fcdb38c
post-merge is a command published in the GitHub repository SAGAAIDEV/mcp-ahrefs (0 stars, last pushed 1y ago), licensed MIT. It adds 15 tokens to every session and 455 once invoked, about $0.0001 per session on Opus 5.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
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.
codex-review
Use when asked to check, turn on, turn off, or switch this repo's Codex review mode (local, github, or off), or to report the effective mode and Codex sandbox status.