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 skills/rohanmistry231/claude-code-project-structure-learning-repository/code-reviewnpx skills add rohanmistry231/Claude-Code-Project-Structure-Learning-Repository --skill code-reviewgit clone --depth 1 https://github.com/rohanmistry231/Claude-Code-Project-Structure-Learning-RepositoryWrote 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/rohanmistry231/claude-code-project-structure-learning-repository/code-review)<a href="https://agentmods.dev/skills/rohanmistry231/claude-code-project-structure-learning-repository/code-review"><img src="https://agentmods.dev/badge/skills/rohanmistry231/claude-code-project-structure-learning-repository/code-review.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.00471 |
| Opus 5 | $0.00000 | $0.00235 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
code-review 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 5d 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.
What it actually says
Skill: Code Review
Description
Perform a thorough code review of changed or specified files, checking for bugs, security issues, style violations, and adherence to the project's CLAUDE.md rules.
When to Use
Trigger this skill when the user says:
- "review this", "review my code", "code review"
- "check for issues", "look for bugs"
- "/review"
Instructions
You are performing a code review for the Blog API project. Follow these steps in order:
Step 1 — Understand the change
Read the files provided or recently edited. If the user didn't specify files, check git diff HEAD
to find what changed.
Step 2 — Check against CLAUDE.md rules
Go through each rule in CLAUDE.md and verify the code does not violate it:
- No
SELECT *in raw SQL - Every route has a docstring
- Schemas are in
schemas.py, not inline - DB writes go through service functions in
arc/services/ - No
print()statements - Errors use
HTTPException
Step 3 — Check for common bugs
- Unhandled edge cases (empty list, None values, 0 IDs)
- Missing input validation
- Off-by-one errors in pagination
- N+1 query problems (loading related objects in a loop)
Step 4 — Check for security issues
- SQL injection risk (raw string interpolation in queries)
- Missing authentication on protected routes
- Sensitive data (passwords, tokens) returned in responses
- CORS settings that are too permissive
Step 5 — Style & readability
- Function names are snake_case
- Variable names are descriptive
- No functions longer than 40 lines
Output Format
Structure your review as:
## Code Review: <filename(s)>
### Critical Issues (must fix)
- <issue>: <file>:<line> — <explanation>
### Warnings (should fix)
- <issue>: <file>:<line> — <explanation>
### Suggestions (optional improvements)
- <suggestion>
### Verdict
APPROVE / REQUEST CHANGES
If there are no issues, say "LGTM — no issues found." with a one-line summary.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 68 lines · 0 tokens per session scan A a78e6e58bb2e
code-review is a skill published in the GitHub repository rohanmistry231/Claude-Code-Project-Structure-Learning-Repository (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 471 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 skills, from other repositories
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
gitnexus
将 GitNexus 作为受控可选代码智能能力接入，用于 brownfield MCP 查询、影响面分析、 detectchanges、多仓分析和更深代码图谱证据。输出必须回落到 /team- 主链和 artifacts。.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.