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 agentmods add agents/mdelapenya/coding-skills/claudegit clone --depth 1 https://github.com/mdelapenya/coding-skillsWrote 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/agents/mdelapenya/coding-skills/claude)<a href="https://agentmods.dev/agents/mdelapenya/coding-skills/claude"><img src="https://agentmods.dev/badge/agents/mdelapenya/coding-skills/claude.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00542 |
| Opus 5 | $0.00000 | $0.00271 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
claude 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code
Topic file for running pr-reviewer from inside Claude Code.
Fetch tooling
Claude Code has the Bash tool. The skill drives the fetch itself using gh (GitHub) or glab (GitLab) — you do not need to pre-load anything before invoking /pr-reviewer. Two ways to invoke it:
- From inside the matching repo:
/pr-reviewer— review the currently checked-out PR branch/pr-reviewer <num>— clone PR<num>from the current repo's remote into a temp dir and review it
- From a barebones directory (no git repo needed):
/pr-reviewer https://github.com/<org>/<repo>/pull/<n>— clones into cwd if it is empty, otherwise into temp/pr-reviewer <org>/<repo>#<n>(GitHub) or<group>/<project>!<n>(GitLab) shorthand — same behavior
Looping primitive
Claude Code ships a /loop slash command (verified at the time of writing):
/loop /pr-reviewer [<num>]
This re-invokes the skill repeatedly, model-paced (omit the interval). Each iteration:
- Re-establishes PR context (re-fetches via
gh/glab) and reuses the existing clone, refreshing it withgit fetch && git reset --hard. - Runs one full round of the skill.
- Appends to
<base-dir>/findings.md.
Recommended flow:
- Run
/pr-reviewer [<num>]once to produce round 1. - If round 1 finishes without converging and you want iteration:
/loop /pr-reviewer [<num>] - The loop exits naturally when:
- The skill writes
converged: truetofindings.md - The skill reaches
--rounds=N - The user stops the loop
- The skill writes
Timed loop (PR still moving)
If the author is actively pushing commits, use a timed loop so each iteration re-fetches at a sensible cadence:
/loop 10m /pr-reviewer [<num>]
Posting the final report
The skill prints the report by default. To post it on GitHub:
gh pr review <pr-number> --comment --body-file <path-the-skill-printed>
Always confirm with the user before posting — a review is visible to others.
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 · 59 lines · 0 tokens per session scan A c9d56a0bc8aa
claude is an agent published in the GitHub repository mdelapenya/coding-skills (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 542 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.