analyze-codebase

analyze-codebase is a skill for Claude Code, Codex from SkeneTechnologies/skene. It costs 50 tokens per session (467 once invoked), scanned A, original, MIT.

A command-line analysis of a codebase focused on product-led growth, or features that help a product attract, activate, and retain users. It detects the technology stack, existing growth features, and possible revenue opportunities.

In plain words
What is it for?
Use it to scan a codebase for growth features and revenue opportunities, then review the generated analysis and plan follow-up work.
Why use it?
It provides findings from the project’s analysis tool instead of relying on manual guesses. If the required configuration or command fails, it reports the failure rather than inventing results.

Skill for Claude CodeCodex

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 skills/skenetechnologies/skene/analyze-codebase
Any agent
npx skills add SkeneTechnologies/skene --skill analyze-codebase
Clone the repo
git clone --depth 1 https://github.com/SkeneTechnologies/skene

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-codebase

README.md
[![agentmods](https://agentmods.dev/badge/skills/skenetechnologies/skene/analyze-codebase.svg)](https://agentmods.dev/skills/skenetechnologies/skene/analyze-codebase)
Your own site
<a href="https://agentmods.dev/skills/skenetechnologies/skene/analyze-codebase"><img src="https://agentmods.dev/badge/skills/skenetechnologies/skene/analyze-codebase.svg" alt="Measured on agentmods" 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 467 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.00050 $0.00467
Opus 5 $0.00025 $0.00234
Sonnet 5 $0.00010 $0.00093
Haiku 4.5 $0.00005 $0.00047

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

Security

Grade A, and why

analyze-codebase 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 3d 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.

cursor-plugin/skills/analyze-codebase/SKILL.md · 49 lines

What it actually says

Analyze Codebase

Run the Skene CLI to analyze the codebase. The CLI does the analysis, not you.

Critical rule

Do NOT substitute your own PLG analysis, findings, or guesses if the CLI fails. Run the CLI, present its output on success, report the error on failure. That's it.

Agent behavior rules

  • Autonomous. Run the CLI, present results, suggest next step. No mid-flow questions.
  • User cannot type into agent terminals. The agent handles all CLI input. Pipe safe defaults for routine prompts. Kill stuck terminals and re-run with piped input.

Steps

  1. Discover CLI options Run uvx skene analyze --help to see available flags. Use only flags that appear in the output.

  2. Verify configuration ls .skene.config 2>/dev/null — if missing: "Run /skene-init first." Stop.

  3. Run analysis Default to project root. Choose appropriate flags based on --help output.

    uvx skene analyze .
    

    Tell the user: "Running analysis, this may take a few minutes."

  4. Handle result

    • Success: Read results from .skene/analysis/, skene-context/, or legacy skene/ and present them. Suggest /skene-plan.
    • Failure: Report the exact error, suggest a fix, stop. Do NOT generate your own analysis.

Error handling

  • 429 / quota: "LLM provider quota error. Check billing, then re-run."
  • Permission errors: Give user the command to run in their own terminal.
  • Timeout: "Try a smaller directory."
  • Any other error: Report verbatim.

Output

Success: CLI results + "Run /skene-plan next." Failure: Error + fix suggestion. No substitute analysis.

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. 3d ago First seen · 49 lines · 50 tokens per session scan A bdc73671e71c

Subscribe to this mod's changes

analyze-codebase is a skill published in the GitHub repository SkeneTechnologies/skene (121 stars, last pushed 8d ago), licensed MIT. It adds 50 tokens to every session and 467 once invoked, about $0.0003 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.