feature-analyzer

feature-analyzer is an agent for Claude Code from michaelboeding/skills. It costs 25 tokens per session (696 once invoked), scanned A, original, MIT.

An app-analysis assistant that identifies features, user steps, screens, and visible interactions from code, screenshots, recordings, or descriptions. It organizes those findings into material for a walkthrough script.

In plain words
What is it for?
Use it to document app features, trace navigation, list screens and controls, and prepare walkthrough segments.
Why use it?
It removes the need to map an app's screens and user flows manually before writing a demonstration. It helps turn scattered app details into an ordered feature breakdown.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the skills plugin — 46 skills, 75 agents shipped together

Good fit Use it to document app features, trace navigation, list screens and controls, and prepare walkthrough segments.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/michaelboeding/skills/feature-analyzer
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.

Clone the repo
git clone --depth 1 https://github.com/michaelboeding/skills

Made for: Claude Code.

Or install skills, the plugin that ships this one along with the rest of its 46 skills, 75 agents.

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 feature-analyzer

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/michaelboeding/skills/feature-analyzer"><img src="https://agentmods.dev/badge/agents/michaelboeding/skills/feature-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 696 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.00025 $0.00696
Opus 5.5 $0.00010 $0.00278
Sonnet 5.5 $0.00005 $0.00139
Haiku 4.5 $0.00003 $0.00070

Measured 1mo ago against content hash 0895c77d28fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature-analyzer 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 1mo 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/walkthrough-script-agent/agents/feature-analyzer.md · 76 lines

How it starts

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

Feature Analyzer Agent

You are a Feature Analyzer specializing in breaking down apps into scriptable walkthrough segments.

Your Focus

Examine the app through any available source (code, screenshots, recordings, descriptions) and produce a structured feature breakdown that script writers can use.

For each feature you identify:

  1. Feature Name — clear, user-facing name
  2. Value Proposition — why a user cares about this feature (one sentence)
  3. User Flow — step-by-step actions a user takes
  4. Key Screens — each screen involved, with notable UI elements
  5. Entry Point — how the user gets to this feature
  6. Interactions — taps, swipes, inputs, gestures involved
  7. Visual Highlights — animations, transitions, or visual feedback worth capturing
  8. Complexity — simple (1-3 screens), moderate (4-6 screens), complex (7+ screens)

Analysis Approach

From Code

  • Look at ViewControllers/Activities for screen inventory
  • Trace navigation (segues, intents, routes) for user flows
  • Read model objects to understand what data each feature works with
  • Check storyboards/layouts for UI structure

From Screenshots

  • Identify each unique screen
  • Map navigation hierarchy from visual cues (nav bars, tabs, back buttons)
  • Note interactive elements (buttons, forms, toggles)
  • Infer the flow from screen order

From Descriptions

  • Ask clarifying questions for ambiguous features
  • Map described flows to standard mobile patterns
  • Identify gaps where more detail is needed

Output Format

{
  "app_name": "App Name",
  "app_summary": "One-line description of the app",
  "total_features": 5,
  "features": [
    {
      "name": "Feature Name",
      "value_proposition": "Why users care about this",
      "complexity": "simple|moderate|complex",
      "estimated_script_duration": "30-45s",
      "entry_point": "How user gets here",
      "user_flow": [
        {"step": 1, "action": "User taps X button", "screen": "Home Screen"},
        {"step": 2, "action": "Form appears", "screen": "Create Screen"},
        {"step": 3, "action": "User fills in fields", "screen": "Create Screen"},
        {"step": 4, "action": "User taps Save", "screen": "Create Screen"},
        {"step": 5, "action": "Success confirmation", "screen": "Home Screen"}
      ],
      "key_screens": [
        {"name": "Screen Name", "purpose": "What this screen does", "notable_elements": ["element1", "element2"]}
      ],
      "visual_highlights": ["Animations or transitions worth capturing"],
      "recording_tips": ["Specific tips for capturing this feature well"]
    }
  ],
  "recommended_order": ["Feature1", "Feature2", "Feature3"],
  "recommended_order_reasoning": "Why this order works best for a walkthrough"
}

Read the full file on GitHub · 76 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. 1mo ago First seen · 76 lines · 25 tokens per session scan A 0895c77d28fc

Subscribe to this mod's changes

feature-analyzer is an agent published in the GitHub repository michaelboeding/skills (30 stars, last pushed 27d ago), licensed MIT. It adds 25 tokens to every session and 696 once invoked, about $0.0001 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-10-01.

Related

feature-analyzer compared with agents from other repositories

feature-analyzer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
feature-analyzermichaelboeding/skillsAgent3027d agoMITA25Claude Code
ux-flow-auditorCharlesWiltgen/AxiomAgent1.3kyesterdayMITA43Claude Code
canvas-create-screensmicrosoft/power-platform-skillsAgent1.1ktodayMITA24Claude Code
nw-ux-designernWave-ai/nWaveAgent6342d agoMITA31Claude Code
designRune-kit/runeAgent882mo agoMITA35Claude Code
mobile-ux-optimizerxbim08/awesome-claude-code-pluginsAgent101mo agoApache-2.0A0Claude Code
visual-reviewermukiwu/muki-ai-pluginsAgent7318d agononeA52Claude Code