agentmods.dev

analyze

A command that builds an inventory of an existing product by scanning its codebase and asking about the business. It records user-facing features, technical constraints, hard-to-copy parts, and areas of technical debt; technical debt is code or design work that may make future changes harder.

In plain words
What is it for?
Use it to map routes, interface components, API endpoints, and database models, then save a product inventory and architecture notes for later planning.
Why use it?
It creates a shared description of what the product already does before planning more work. This reduces guesswork when choosing features or investigating architecture.

Command

483 1mo ago A scan 8 tokens original MIT
View the source file ooiyeefei/ccc
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.

agentmods
npx agentmods add commands/ooiyeefei/ccc/analyze
Clone the repo
git clone --depth 1 https://github.com/ooiyeefei/ccc
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 306 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00008 $0.00306
Opus 5 $0.00004 $0.00153
Sonnet 5 $0.00002 $0.00061
Haiku 4.5 $0.00001 $0.00031

Measured 2d ago against content hash c2c3659a80a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

plugins/product-management/commands/analyze.md · 53 lines

What it actually says

Product Analysis

Perform comprehensive product analysis to understand current state.

Process

  1. Scan Codebase Structure

    • Use Glob to find routes/pages (user-facing features)
    • Identify components (UI capabilities)
    • Find API endpoints (backend functionality)
    • Locate database models (data entities)

  2. Interview User for business context using AskUserQuestion:

    • "What's your core value proposition?"
    • "Who are your target users?"
    • "What's your pricing model?"
    • "What do users love most? Complain about most?"

  3. Generate Product Inventory

    • List all features with metadata
    • Identify technical moats (hard to replicate)
    • Flag technical debt areas
    • Note architectural constraints

  4. Save Results

    • Create .pm/ directory if not exists
    • Save to .pm/product/inventory.md
    • Save to .pm/product/architecture.md
    • Update .pm/cache/last-updated.json

Output Format

# Product Inventory - [Date]

## Core Value Proposition
[User-provided]

## Features
| Feature | Type | Technical Moat | Debt Level |
|---------|------|----------------|------------|

## Architecture Constraints
- [Constraint 1]

Reference the product-management skill for detailed guidance.

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. 2d ago First seen · 53 lines · 8 tokens per session scan A c2c3659a80a8

Subscribe to this mod's changes

analyze is a command published in the GitHub repository ooiyeefei/ccc (483 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 306 once invoked, about $0.0000 per session on Opus 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-30.

Backend and APIsDatabasesWriting and docs
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens