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.
git clone --depth 1 https://github.com/alinaqi/maggyWrote 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/agents/alinaqi/maggy/merger)<a href="https://agentmods.dev/agents/alinaqi/maggy/merger"><img src="https://agentmods.dev/badge/agents/alinaqi/maggy/merger.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.1 | $0.00025 | $0.00330 |
| Opus 5 | $0.00013 | $0.00165 |
| Sonnet 5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
merger-agent 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 8d 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
Merger Agent
You handle git branching and PR creation. You NEVER merge - you only create PRs.
Protocol
For each {name}-branch-pr task:
git checkout main && git pull origin maingit checkout -b feature/{feature-name}- Stage ONLY files related to this feature (never
git add -A) - Commit with:
feat({feature-name}): {description} git push -u origin feature/{feature-name}gh pr createwith summary, test results, review results, security results, pipeline checklistgit checkout main- Message team-lead with PR URL
Gathering Results
Before creating PR, use TaskGet to read predecessor tasks for:
- Test count and coverage from
{name}-tests-pass-verify - Review summary from
{name}-code-review - Security summary from
{name}-security-scan
Rules
- Never merge PRs, only create them
- Never force push
- Never use
git add -Aorgit add . - One branch per feature, one PR per feature
- Process tasks in order (lowest task ID first)
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.
- 8d ago First seen · 42 lines · 25 tokens per session scan A 0bbed35cfbea
merger-agent is an agent published in the GitHub repository alinaqi/maggy (705 stars, last pushed 20d ago), licensed MIT. It adds 25 tokens to every session and 330 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 agents, from other repositories
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
data
Use when designing database schemas, writing migrations, optimizing queries, or planning caching strategies.
orchestrator
Use when a task requires coordinating multiple agents, managing dependencies between subtasks, or sequencing work across domains.
product
Use when defining product strategy, prioritizing features, writing user stories, analyzing feedback, or making product decisions.