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 skills add MereWhiplash/engram-cogitator --skill finishing-branchgit clone --depth 1 https://github.com/MereWhiplash/engram-cogitatorWrote 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/skills/merewhiplash/engram-cogitator/finishing-branch)<a href="https://agentmods.dev/skills/merewhiplash/engram-cogitator/finishing-branch"><img src="https://agentmods.dev/badge/skills/merewhiplash/engram-cogitator/finishing-branch/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/skills/merewhiplash/engram-cogitator/finishing-branch"><img src="https://agentmods.dev/badge/skills/merewhiplash/engram-cogitator/finishing-branch.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.00021 | $0.00844 |
| Opus 5 | $0.00010 | $0.00422 |
| Sonnet 5 | $0.00004 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
finishing-branch 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 11d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finishing a Branch
Complete development work with verification, memory storage, and merge options.
Announce: "I'm using the finishing-branch skill to complete this work."
The Flow
Verify Tests → EC Review → Present Options → Execute
Step 1: Verify Tests @verifying
Load project config:
ec_search:
query: project config
type: config
Run all verifications:
{test_command}
{lint_command}
{build_command}
If failures: Stop. Fix using @debugging before proceeding.
If passing: Continue.
Step 2: EC Review
Before finishing, review what's worth remembering.
Look at what changed:
git log --oneline main..HEAD
git diff --stat main..HEAD
Use AskUserQuestion:
{
"questions": [{
"question": "Any decisions, learnings, or patterns worth storing in EC?",
"header": "Memory",
"options": [
{ "label": "Yes", "description": "I'll describe what to store" },
{ "label": "No", "description": "Nothing notable this time" },
{ "label": "Let me suggest", "description": "Claude proposes, I approve" }
],
"multiSelect": false
}]
}
If "Let me suggest" - analyze the changes and propose:
- decisions - Architectural choices made
- learnings - Gotchas discovered during implementation
- patterns - New conventions established
For each approved memory:
ec_add:
type: decision|learning|pattern
area: [component]
content: [What to remember]
rationale: [Why it matters]
Step 3: Present Options
Load branch convention:
ec_search:
query: project config branch
type: config
{
"questions": [{
"question": "How do you want to finish this branch?",
"header": "Finish",
"options": [
{ "label": "Create PR", "description": "Push and open pull request" },
{ "label": "Merge locally", "description": "Merge to main locally" },
{ "label": "Keep as-is", "description": "I'll handle it later" },
{ "label": "Discard", "description": "Delete this branch and work" }
],
"multiSelect": false
}]
}
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.
- 11d ago First seen · 165 lines · 21 tokens per session scan A b082bbffe62e
finishing-branch is a skill published in the GitHub repository MereWhiplash/engram-cogitator (4 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 844 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 skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…