Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rjmurillo/ai-agents/plugin install project-toolkitWrote 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/rjmurillo/ai-agents/repository-completion-proof)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/repository-completion-proof"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/repository-completion-proof/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/rjmurillo/ai-agents/repository-completion-proof"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/repository-completion-proof.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.00034 | $0.01685 |
| Opus 5.5 | $0.00014 | $0.00674 |
| Sonnet 5.5 | $0.00007 | $0.00337 |
| Haiku 4.5 | $0.00003 | $0.00169 |
Grade A, and why
repository-completion-proof 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 3d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository completion proof
Requires the rjmurillo/ai-agents checkout and its contributor-only sibling skills.
Inputs: PR number, intended acceptance criteria, and authorized task scope.
Apply the common execution contract.
Reuse the review config, pr-comment-responder, and the existing completion dispatcher.
This shortcut joins execution trust, criterion results, and platform acceptance.
Triggers
prove an ai-agents PR is completeverify before dispatching review commandsreview is finished but completion is uncertain
Process
Phase 1: Prove execution trust before dispatching review commands
Read config resolution in pr-review.
Use that documentation without invoking its standalone orchestration workflow.
Use its command map for that host rather than inventing a launcher.
Resolve the selected config's absolute path through that maintained resolution procedure.
For each invocation, bind PR_NUMBER and PR_REVIEW_CONFIG from the current task.
Do not rely on variables surviving separate tool shells.
From the repository root, the POSIX checkout form is:
GITHUB_SCRIPTS="${COPILOT_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-.claude}}/skills/github/scripts"
: "${PR_NUMBER:?Set the task PR number in this invocation}"
: "${PR_REVIEW_CONFIG:?Set the selected absolute config path in this invocation}"
uv run python "$GITHUB_SCRIPTS/pr/run_completion_gate.py" --config "$PR_REVIEW_CONFIG" --pull-request "$PR_NUMBER" --verify-config-only --json
Keep the default trusted remote-tracking ref unless the selected base requires another.
Any alternate anchor must resolve under refs/remotes/.
Do not substitute HEAD or a movable local branch to silence divergence.
Check anchor freshness against the selected remote revision through supported reads.
Fetching changes local Git state and requires the task's authority.
| Observation | Branch |
|---|---|
Successful verification and verified: true |
Begin verified finding handling. No completion claim follows yet. |
| Untrusted config or command file | Preserve the surfaced difference for human inspection. |
| Verification impossible | Restore verifiable Git evidence through an authorized owner; do not dispatch. |
| Installed config accepted by origin | Retain origin and command-trust evidence; run criteria before claiming success. |
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.
- 3d ago First seen · 163 lines · 34 tokens per session scan A a2581693f473
repository-completion-proof is a skill published in the GitHub repository rjmurillo/ai-agents (48 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,685 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-10-15.
Other skills, from other repositories
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
babysit
Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.
make-pr-easy-to-review
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".
github-review-pr
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…
review-this-branch
Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.