analyze-project

analyze-project is a skill for Claude Code, Codex from marysatasselshaped667/skills-collection-1. It costs 39 tokens per session (2,900 once invoked), scanned A, a copy of analyze-project, MIT.

A forensic workflow for reviewing AI-assisted coding sessions and explaining what changed, what caused problems, and where work was repeated. It examines session records from Antigravity and separates user changes, agent mistakes, codebase friction, testing issues, and task complexity.

In plain words
What is it for?
Use it to find recurring problem areas, assess whether prompts were clear, identify root causes, and improve future coding sessions.
Why use it?
It helps teams understand why a coding task became difficult instead of judging the outcome from iteration counts alone.

Skill for Claude CodeCodex

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

Good fit Use it to find recurring problem areas, assess whether prompts were clear, identify root causes, and improve future coding sessions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/marysatasselshaped667/skills-collection-1/analyze-project
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 marysatasselshaped667/skills-collection-1 --skill analyze-project
Clone the repo
git clone --depth 1 https://github.com/marysatasselshaped667/skills-collection-1

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 analyze-project

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/marysatasselshaped667/skills-collection-1/analyze-project"><img src="https://agentmods.dev/badge/skills/marysatasselshaped667/skills-collection-1/analyze-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,900 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 100% copy Near-identical to another mod 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.00039 $0.02900
Opus 5 $0.00019 $0.01450
Sonnet 5 $0.00008 $0.00580
Haiku 4.5 $0.00004 $0.00290

Measured 8d ago against content hash a8bc543e494b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

analyze-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 8d 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.

Origin

This is a copy

100% identical to analyze-project — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

SKILLS/analyze-project/SKILL.md · 435 lines

How it starts

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

/analyze-project — Root Cause Analyst Workflow

Analyze AI-assisted coding sessions in ~/.gemini/antigravity/brain/ and produce a report that explains not just what happened, but why it happened, who/what caused it, and what should change next time.

Goal

For each session, determine:

  1. What changed from the initial ask to the final executed work
  2. Whether the main cause was:
    • user/spec
    • agent
    • repo/codebase
    • validation/testing
    • legitimate task complexity
  3. Whether the opening prompt was sufficient
  4. Which files/subsystems repeatedly correlate with struggle
  5. What changes would most improve future sessions

Global Rules

  • Treat .resolved.N counts as iteration signals, not proof of failure
  • Separate human-added scope, necessary discovered scope, and agent-introduced scope
  • Separate agent error from repo friction
  • Every diagnosis must include evidence and confidence
  • Confidence levels:
    • High = direct artifact/timestamp evidence
    • Medium = multiple supporting signals
    • Low = plausible inference, not directly proven
  • Evidence precedence:
    • artifact contents > timestamps > metadata summaries > inference
  • If evidence is weak, say so

Step 0.5: Session Intent Classification

Classify the primary session intent from objective + artifacts:

  • DELIVERY
  • DEBUGGING
  • REFACTOR
  • RESEARCH
  • EXPLORATION
  • AUDIT_ANALYSIS

Record:

  • session_intent
  • session_intent_confidence

Use intent to contextualize severity and rework shape. Do not judge exploratory or research sessions by the same standards as narrow delivery sessions.


Step 1: Discover Conversations

  1. Read available conversation summaries from system context
  2. List conversation folders in the user’s Antigravity brain/ directory
  3. Build a conversation index with:
    • conversation_id
    • title
    • objective
    • created
    • last_modified
  4. If the user supplied a keyword/path, filter to matching conversations; otherwise analyze all

Read the full file on GitHub · 435 lines

Files

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.

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. 8d ago First seen · 435 lines · 39 tokens per session scan A a8bc543e494b

Subscribe to this mod's changes

analyze-project is a skill published in the GitHub repository marysatasselshaped667/skills-collection-1 (1 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 2,900 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to analyze-project, differing in 0 lines, and is treated as a copy.