agentmods.dev

review-project

review-project is a skill for Claude Code, Codex from tomzx/agents. It costs 50 tokens per session (1,374 once invoked), scanned A, original, MIT.

A review of the project information files that explain a codebase, its architecture, infrastructure, conventions, and terminology. It checks whether a new developer or coding agent could understand the project from those files alone.

In plain words
What is it for?
Auditing project overview, architecture, infrastructure, conventions, and vocabulary documents.
Why use it?
It finds missing, outdated, or conflicting context before that information causes incorrect implementation decisions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 13repo +1 changed 16d ago A scan 50 tokens original MIT

Good fit Auditing project overview, architecture, infrastructure, conventions, and vocabulary documents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tomzx/agents/review-project
View source ↗ tomzx/agents tomzx.github.io
Install

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.

Any agent
npx skills add tomzx/agents --skill review-project
Clone the repo
git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for review-project

README.md
[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/review-project/github.svg)](https://agentmods.dev/skills/tomzx/agents/review-project)
Your own site
<a href="https://agentmods.dev/skills/tomzx/agents/review-project"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-project/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.

agentmods 80×15 button for review-project

Your own site · 80×15
<a href="https://agentmods.dev/skills/tomzx/agents/review-project"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,374 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.01374
Opus 5.5 $0.00020 $0.00550
Sonnet 5.5 $0.00010 $0.00275
Haiku 4.5 $0.00005 $0.00137

Measured 16d ago against content hash fa4c48d972c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-project 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 16d 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.

skills/review-project/SKILL.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review Project

Audits the project context files as a set, so downstream skills (create-goals, create-needs-assessment, create-feasibility, the audit family) can rely on them.

The review answers one question: could an agent that has never seen this project orient itself from .sdlc/context/ alone?

Prerequisites

  • Apply the shared SDLC conventions in skills/sdlc/references/shared.md.
  • The context files under .sdlc/context/ (project-overview.md, use-cases.md, architecture.md, infrastructure.md, conventions.md, vocabulary.md), or the equivalent documents provided in context or as file paths.
  • Source code in the project root (optional, for the currency spot-check).

Steps

  1. Read the context files from .sdlc/context/ if present, otherwise from context or as file paths.
  2. Cross-reference the files against each other, and, where code exists, against the repository.
  3. Identify issues in each category below.
  4. Report findings. Omit any category that has no findings.
  5. Write the findings to .sdlc/context/review-project.md with frontmatter artifact: project, verdict (approved if no blocking findings, changes-requested if the author must address findings, rejected for a fundamental flaw), and reviewed_at: <ISO date>, per skills/sdlc/references/shared.md. Record any unresolved open questions in the findings body.

Review Checklist

Completeness

  • Does every section of every context file contain substantive content, with no template placeholders (<...>, "TBD") left?
  • Does use-cases.md list at least one Supported use case, each stating a goal an actor has for using the project and naming that actor?
  • For an empty project, are not-yet-built parts (architecture, infrastructure) explicitly marked as planned rather than presented as existing?
  • Is goals.md absent? Note it as informational with a pointer to /create-goals; it is not a blocker for this review.

Consistency

  • Do terms used in project-overview.md and architecture.md match the definitions in vocabulary.md (no synonym drift, no redefinitions)?
  • Does every component named in architecture.md appear in the infrastructure.md technology stack, or is the gap explained?
  • Does the scope in project-overview.md (in and out) agree with what architecture.md describes, with no out-of-scope components documented as core?
  • Do the Supported use cases in use-cases.md state goals the scope and architecture serve (not a command, route, or UI section for its own sake), and does every Wanted entry carry a signal (an issue, feature, or roadmap reference)?

Read the full file on GitHub · 120 lines

Changes

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.

  1. 16d ago Changed · +3 lines fa4c48d972c2
  2. 22d ago Changed · +1 lines 12f9126c55b8
  3. 23d ago Changed · -4 lines a863967a7a92
  4. 1mo ago First seen · 120 lines · 50 tokens per session scan A bd196b3e3f50

Subscribe to this mod's changes

review-project is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 1,374 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-09-03.

PlanningWriting and docs
Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens