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 arbazkhan971/godmode --skill finishgit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/finish)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/finish"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/finish/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/arbazkhan971/godmode/finish"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/finish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 165 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00049 | $0.01290 |
| Opus 5 | $0.00024 | $0.00645 |
| Sonnet 5 | $0.00010 | $0.00258 |
| Haiku 4.5 | $0.00005 | $0.00129 |
Grade A, and why
finish 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 9d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activate When
/godmode:finish, "done", "merge", "finalize"- Feature branch has commits ahead of main
- Another skill completes and branch is ready
Auto-Detection
Routes here when:
git log main..HEAD --onelinereturns 1+ commits AND user says "done", "merge", "finish"/godmode:buildcompletes all tasks- User explicitly invokes
/godmode:finish
Workflow
1. Snapshot Branch State
branch=$(git branch --show-current)
commits=$(git log main..HEAD --oneline | wc -l | tr -d ' ')
files_changed=$(git diff main..HEAD --stat | tail -1)
echo "Branch: $branch | $commits commits | $files_changed"
# Check if on main
if [ "$branch" = "main" ]; then
echo "ERROR: Already on main. Nothing to finish."
exit 1
fi
2. Enforce Clean Worktree
staged=$(git diff --cached --name-only)
unstaged=$(git diff --name-only)
untracked=$(git ls-files --others --exclude-standard)
IF staged non-empty: STOP — commit or stash first
IF unstaged non-empty: STOP — commit, stash, or discard
IF untracked files: WARN — won't be in merge
3. Run Full Guard Suite
build_cmd && lint_cmd && test_cmd
THRESHOLDS:
Build: must exit 0
Lint: must exit 0 with --max-warnings=0
Tests: 100% pass rate required
IF any failure: STOP, run /godmode:fix first
IF no test runner: WARN, continue
4. Check Merge Conflicts
git fetch origin main
git merge-tree \
$(git merge-base HEAD origin/main) origin/main HEAD
IF conflicts: print files, recommend rebase.
5. Determine Outcome
PRIORITY (first match wins):
DISCARD: user says "discard", "abandon" (confirm)
KEEP: user says "keep", "not yet", "park it"
MERGE: user says "merge" OR PR approved
PR: default when checks pass
6. Execute Outcome
MERGE:
git checkout main && git pull origin main
git merge --squash {branch}
git commit -m "feat({module}): {title}
Squashed {N} commits from {branch}."
git branch -d {branch}
PR:
gh pr create --title "feat({module}): {title}" \
--body "## Changes
$(git log main..HEAD --format='- %s')
## Guard Results
Build: PASS | Lint: PASS | Tests: PASS"
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.
- 9d ago First seen · 189 lines · 49 tokens per session scan A 247b9b0e3619
finish is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 11d ago), licensed MIT. It adds 49 tokens to every session and 1,290 once invoked, about $0.0002 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
manuscript-as-code
Treat manuscripts as software: version control, reproducible builds, figure pipelines, CI, and structured repo layout. Helps teams avoid 'finalv7' chaos and ensures submission-ready artifacts.
ac-commit-manager
Manage git commits for autonomous coding. Use when committing feature implementations, creating descriptive commits, managing git workflow, or handling version control.
ac-checkpoint-manager
Manage checkpoints for rollback capability. Use when creating save points, rolling back changes, managing recovery points, or restoring previous states.
security-review
Local security review of git changes: deterministic scan + Security reviewer over the diff. No API key, no SDK.
rollback
Rolls back git commit, DB migration, or deploy to known-good with safety + health checks. Triggers: rollback, revert deploy, revert migration, rollback commit, git revert.
edit-discipline
Change files with the edit and write tools, never by rewriting them through bash (sed, awk, tee, heredoc, redirection), and show git diff before reporting a file-changing task as done. Triggers: edit, write, modify, refactor, patch, fix, diff, review changes.