Borrowing it
Nothing to install: this file belongs to tugrulguner/summonpot. 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/tugrulguner/summonpot/main/.claude/skills/review-code/SKILL.mdgit clone --depth 1 https://github.com/tugrulguner/summonpotWrote 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/tugrulguner/summonpot/review-code)<a href="https://agentmods.dev/skills/tugrulguner/summonpot/review-code"><img src="https://agentmods.dev/badge/skills/tugrulguner/summonpot/review-code/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/tugrulguner/summonpot/review-code"><img src="https://agentmods.dev/badge/skills/tugrulguner/summonpot/review-code.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.00062 | $0.00866 |
| Opus 5.5 | $0.00025 | $0.00346 |
| Sonnet 5.5 | $0.00012 | $0.00173 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
review-code 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 1mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing a summonpot change
Check the diff against the defects this project has actually shipped, in the order they have cost the most.
1. Does a doc claim something the code does not do?
The most repeated defect here. Shipped examples: stream=True documented as working
while nothing read the flag; method= accepted and discarded; "capabilities themselves
remain deterministic" claiming a guarantee the framework cannot give.
A claim is a defect. Check README.md, ROADMAP.md, docs/, docstrings, and
src/summonpot/templates/skills/summonpot.md.
grep -rn "stream\|method=" README.md docs/ src/summonpot/templates/skills/
2. Does a new guard reject valid code?
Every registration guard needs a false-positive test, not only a true-positive one. Two guards shipped rejecting valid input:
- an unbound-method check that rejected any function whose first parameter was
self; - an annotation check that rejected
request: "Request"whereRequestexisted.
For any new rule, write the case that should still be accepted and run it.
3. Is the failure raised at the right time?
Registration beats request time; request time beats silence. A wrong declaration should
never reach traffic. Summon.__call__() in src/summonpot/summon.py is the registration
entry point. Place each rule in the responsible validation layer — including capability
normalization in src/summonpot/tools.py and contract checks in
src/summonpot/_validation.py — and ensure the entry point invokes it before serving or
execution.
4. Does the test fail without the fix?
Assert it in an isolated worktree so verification cannot modify the reviewer's working tree or any user-owned recovery state. Apply only the test diff to the base revision, then run the focused regression there:
base=${BASE_REF:-origin/main}
red_tree=$(mktemp -d)
git worktree add --detach "$red_tree" "$base"
git diff "$base" -- tests/ | git -C "$red_tree" apply -
(cd "$red_tree" && uv sync --all-extras --locked && uv run pytest tests/ -q)
git worktree remove --force "$red_tree"
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.
- 1mo ago Changed · +14 lines e1d954a39474
- 2mo ago First seen · 77 lines · 62 tokens per session scan A 99c674cf056f
review-code is a skill published in the GitHub repository tugrulguner/summonpot (5 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 866 once invoked, about $0.0002 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
python-testing
Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
code-review
Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.
loop-verifier
Independent verification agent for loop-produced changes. Finds reasons to reject. Runs tests. Confirms diff scope. Use after minimal-fix or any implementer sub-agent — never in the same role as the implementer.
cli-command
Design, implement, or review Composio CLI commands under ts/packages/cli using Effect, effect/cli, services, output conventions, configuration and environment variables, and local vendor references. Use for CLI command UX, command wiring, service changes, or CLI source edits. Do not use for CLI E2E-only work; use…
mcore-linting-and-formatting
Linting and formatting for Megatron-LM. Covers running autoformat.sh, tools (ruff, black, isort, pylint, mypy), and code style rules.