Borrowing it
Nothing to install: this file belongs to g-hyeong/MCP-AidFlow. 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/g-hyeong/MCP-AidFlow/main/.claude/skills/finish/SKILL.mdgit clone --depth 1 https://github.com/g-hyeong/MCP-AidFlowWrote 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/g-hyeong/mcp-aidflow/finish)<a href="https://agentmods.dev/skills/g-hyeong/mcp-aidflow/finish"><img src="https://agentmods.dev/badge/skills/g-hyeong/mcp-aidflow/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/g-hyeong/mcp-aidflow/finish"><img src="https://agentmods.dev/badge/skills/g-hyeong/mcp-aidflow/finish.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.00017 | $0.00943 |
| Opus 5 | $0.00009 | $0.00472 |
| Sonnet 5 | $0.00003 | $0.00189 |
| Haiku 4.5 | $0.00002 | $0.00094 |
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 10d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete the current session by running review, archive, report, and commit sequentially. Stop immediately at any step if a blocking issue is found.
Step 1: Review
-
Identify the active session
- Use
session statusto find the current session and its changed files - Read plan.md to understand what was intended
- Use
-
Code Review - Changed Files Read EVERY changed file and check:
- Does the implementation match plan.md requirements?
- Are there any incomplete TODOs or FIXMEs?
- Error handling: are edge cases covered?
- If SPEC.md exists, do changes follow its conventions?
- Are there any hardcoded values that should be configurable?
- Security: no exposed secrets, no injection vulnerabilities?
-
Consistency Check
- Naming conventions consistent across new/modified code?
- Import patterns match existing codebase style?
- No duplicate logic that should be extracted?
- No dead code or unused imports left behind?
-
Test Coverage
- Run existing tests:
npm test(or project-specific command from SPEC.md) - If tests fail, STOP here and report failures to the user
- Run existing tests:
-
Plan Completion Audit
- Check each Implementation Item and Acceptance Criteria in plan.md
- Ensure all
- [ ]items are checked- [x]if completed - Flag any genuinely unchecked items
-
Review Gate
- If blocking issues found: present them with AskUserQuestion, offer "Fix now" / "Proceed anyway" / "Cancel"
- If "Fix now": fix issues, then restart from Step 1
- If "Cancel": stop entirely
- If no issues or "Proceed anyway": continue to Step 2
Step 2: Archive Session
Run session complete to archive the session.
- If it fails due to incomplete plan items, use
force: true
Step 3: Generate Report
- Find the latest directory in
.aidflow/history/(sorted by name, newest first) - Read
meta.jsonfrom that directory to get session metadata - Read
plan.mdfrom that directory (if exists) - Gather git commits for the session period:
- Use
created_atandcompleted_atfrom meta.json as the time range - Run:
git log --oneline --after="{created_at}" --before="{completed_at}"
- Use
- Read the changed files listed in meta.json and briefly review each
- Write
report.mdin the history directory with this format:
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.
- 10d ago First seen · 112 lines · 17 tokens per session scan A 34b30467dffd
finish is a skill published in the GitHub repository g-hyeong/MCP-AidFlow (0 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 943 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.
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…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.