Borrowing it
Nothing to install: this file belongs to janeksm/mcp-digger. 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/janeksm/mcp-digger/main/.claude/skills/accept/SKILL.mdgit clone --depth 1 https://github.com/janeksm/mcp-diggerWrote 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/janeksm/mcp-digger/accept)<a href="https://agentmods.dev/skills/janeksm/mcp-digger/accept"><img src="https://agentmods.dev/badge/skills/janeksm/mcp-digger/accept/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/janeksm/mcp-digger/accept"><img src="https://agentmods.dev/badge/skills/janeksm/mcp-digger/accept.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.00023 | $0.01259 |
| Opus 5.5 | $0.00009 | $0.00504 |
| Sonnet 5.5 | $0.00005 | $0.00252 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade A, and why
accept 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accept Step
Finalize the current implementation step with quality gates before committing. Updates CMCM knowledge files (patterns, handoff).
Step to accept: $ARGUMENTS (if empty, infer from TODO.md — the first step with status in-progress)
Instructions
1. Identify the step
Read TODO.md to find the step:
- If
$ARGUMENTSis a number, use that step. - Otherwise find the first
in-progressstep. - If no
in-progressstep exists, inspectgit diff HEADandgit statusto summarize changes, pick the next step number, and add a new row with statusin-progress.
2. Simplify (analyze + fix)
Review changed files and apply simplification fixes:
- Read
CC.mdfirst — Node.js / TypeScript clean code rules apply here as the simplify checklist. - Run
git diff HEADto identify changed files and hunks. - For each changed area, check for: deep nesting (use guard clauses), long functions (split), generic names (make descriptive), dead code (remove), redundant abstractions (inline), unnecessary comments (delete), plus the rules in
CC.md(non-null assertions, floating promises,anytypes, missing return types on exports, etc.). - Apply fixes incrementally — one at a time.
- After all simplify fixes, verify: run
npm run typecheck,npm run lint,npm test(as separate commands). - If verification fails, fix the failure before continuing.
- Record what was fixed for the summary in step 5.
3. Codex review (on post-simplify code)
Remove any previous CODEX_REVIEW.md. Then launch Codex CLI in background (Bash with run_in_background: true):
codex exec -s read-only -o CODEX_REVIEW.md "You are a senior code reviewer. Review the recent changes (unstaged and staged diffs) in this codebase.
For each finding report:
- Severity: CRITICAL, HIGH, MEDIUM, or LOW
- File path and line number
- What the issue is
- Suggested fix (code snippet if applicable)
Group by severity (CRITICAL first). Format as markdown checklist with - [ ] items." < /dev/null
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 · 111 lines · 23 tokens per session scan A 95cfd0e8d7bd
accept is a skill published in the GitHub repository janeksm/mcp-digger (0 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 1,259 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 skills, from other repositories
git-workflow
Follow this team's Git conventions for branching, commit messages, and pull requests.
cratis-commits-and-pull-requests
Use before writing commit messages, staging, pushing or creating and editing PRs, including release labels and issue references. Not for candidate assembly, issue status or batching release windows.
changelog
Auto-generate changelog from git commits — grouped by feat/fix/docs with PR links.
kibi-commit-review
Use when kibi check --staged or the Kibi pre-commit hook blocks a commit (kibiimpactevidencemissing, symbolsmanifeststale, symbolgranularityviolation, symbol-coverage, kibi check-generated drift, Staged impact review failed), or when preparing a commit or pull-request impact review. Covers reading the per-file Detail…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
dev6-review-fix
Apply fixes for review comments from dev5-review and commit. Sub-skill of the /dev workflow.