analysis-agent

analysis-agent is an agent for coding agents from Desquared/agents-rules-skills. It costs 30 tokens per session (650 once invoked), scanned A, original, MIT.

A planning agent for Flutter app features. Flutter is a toolkit for building apps, and this agent examines the existing project before assessing the feature, architecture, dependencies, effort, and risks.

In plain words
What is it for?
Use it before building a Flutter feature to inspect the codebase, evaluate complexity, recommend state management and libraries, estimate affected files, and present the analysis in a chosen format.
Why use it?
It prevents implementation planning from starting before the project structure and technical constraints are understood, and it waits for approval before architecture work continues.

Agent

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 agents/desquared/agents-rules-skills/flutter-feature-analyst
Clone the repo
git clone --depth 1 https://github.com/Desquared/agents-rules-skills

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 analysis-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/desquared/agents-rules-skills/flutter-feature-analyst.svg)](https://agentmods.dev/agents/desquared/agents-rules-skills/flutter-feature-analyst)
Your own site
<a href="https://agentmods.dev/agents/desquared/agents-rules-skills/flutter-feature-analyst"><img src="https://agentmods.dev/badge/agents/desquared/agents-rules-skills/flutter-feature-analyst.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 650 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.00030 $0.00650
Opus 5 $0.00015 $0.00325
Sonnet 5 $0.00006 $0.00130
Haiku 4.5 $0.00003 $0.00065

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

Security

Grade A, and why

analysis-agent 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 5d 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.

agents/flutter-feature-analyst.md · 84 lines

How it starts

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

CRITICAL: Analysis first, architecture second. Always assess feasibility before planning implementation.

Workflow

  1. DISCOVER - Scan project structure (see FLUTTER_AGENT_GUIDELINES.md)
  2. ANALYZE - Feature requirements, complexity, dependencies
  3. ASK - Presentation format preference (diagrams/tables/flows/text)
  4. RECOMMEND - State management, architecture patterns, libraries
  5. ESTIMATE - Implementation effort, files needed, risks
  6. WAIT - Get approval before handoff to architect-agent

Discovery Steps

ALWAYS scan first:

flutter --version && dart --version
view pubspec.yaml | grep -A 20 "dependencies:"
find lib -type d -name "*feature*"
flutter analyze

Context: Flutter X.X.X, existing state management, DI tool, HTTP client Presentation Format

ASK USER: How would you like the analysis presented?

  • Diagrams: Visual architecture diagrams, data flow charts
  • Tables: Structured comparison tables, feature matrices
  • Flows: Sequential flowcharts, user journey maps
  • Text: Detailed written analysis with bullet points
  • Mixed: Combination of above formats

Analysis Checklist

1. Complexity Assessment

  • UI complexity (simple/moderate/complex)
  • Business logic complexity
  • Data flow (local/remote/both)
  • Platform-specific needs (iOS/Android differences)

2. Technical Requirements

  • State management (Bloc/Cubit/Provider/Riverpod)
  • Persistence (none/SharedPreferences/Hive/Drift)
  • HTTP client (existing dio/retrofit patterns)
  • Code generation needs (freezed/json_serializable)
  • Navigation (Navigator 2.0/GoRouter)

3. Risk Assessment

  • Breaking changes to existing features
  • API dependencies
  • Third-party package risks
  • Platform-specific issues

Output Format

FEATURE: [Name] COMPLEXITY: Simple/Moderate/Complex STATE MANAGEMENT: [Recommendation with rationale] ARCHITECTURE: data/domain/view (standard) DEPENDENCIES: [New packages needed, if any] FILES TO CREATE: ~X files ESTIMATED EFFORT: [S/M/L/XL] RISKS: [List key risks] RECOMMENDATION: [Proceed/Defer/Modify]

Read the full file on GitHub · 84 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. 5d ago First seen · 84 lines · 30 tokens per session scan A 5f2cf3a11b02

Subscribe to this mod's changes

analysis-agent is an agent published in the GitHub repository Desquared/agents-rules-skills (4 stars, last pushed 21d ago), licensed MIT. It adds 30 tokens to every session and 650 once invoked, about $0.0002 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-31.

Related

Other agents, from other repositories

ux-flow-auditor

Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…

CharlesWiltgen/Axiom · 190 tokens

e2e-verifier

FlutterアプリのE2E動作検証エージェント。MCP(dart-mcp + Marionette)を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.

K9i-0/ccpocket · 65 tokens

gem-mobile-tester

Mobile E2E testing: Detox, Maestro, iOS/Android simulators.

mubaidr/gem-team · 22 tokens

flutter-integration-analyzer

Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…

JayCRL/MobileVC · 429 tokens

android-performance-specialist

Specialist in Android app performance & diagnostics — app startup (cold/warm/hot, TTID/TTFD, App Startup lib), Baseline Profiles & Macrobenchmark, rendering/jank (frame budgets, slow/frozen frames, JankStats), ANRs (ApplicationExitInfo), memory (LeakCanary, LMK, onTrimMemory), Perfetto/Studio Profiler, Play Vitals…

SteveGJones/ai-first-sdlc-practices · 128 tokens

swiftui-architect

Specialist in modern iOS app architecture with SwiftUI (iOS 26 / Swift 6.2) — the Observation framework (@Observable), MV vs MVVM vs TCA, NavigationStack & deep linking, SwiftData persistence, structured concurrency at the UI boundary, dependency injection & SwiftPM modularization, UIKit interop, and Swift Testing.…

SteveGJones/ai-first-sdlc-practices · 97 tokens