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.
npx agentmods add skills/mdazadhossain95/flutter-agent-skills/flutter-explain-codebasenpx skills add mdazadhossain95/flutter-agent-skills --skill flutter-explain-codebasegit clone --depth 1 https://github.com/mdazadhossain95/flutter-agent-skillsWrote 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.
[](https://agentmods.dev/skills/mdazadhossain95/flutter-agent-skills/flutter-explain-codebase)<a href="https://agentmods.dev/skills/mdazadhossain95/flutter-agent-skills/flutter-explain-codebase"><img src="https://agentmods.dev/badge/skills/mdazadhossain95/flutter-agent-skills/flutter-explain-codebase.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00041 | $0.00702 |
| Opus 5 | $0.00020 | $0.00351 |
| Sonnet 5 | $0.00008 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
flutter-explain-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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explain Flutter Codebase
Purpose
Use this skill to analyze and explain an existing Flutter codebase quickly and clearly for onboarding, handoff, debugging, and planning refactors.
Activation
Activate when the user asks to explain a Flutter app, module, architecture, folder structure, or how parts of the codebase work together.
Inputs
Collect minimal context before analysis:
- Scope: whole project, feature folder, or specific files.
- Goal: onboarding, debugging, architecture review, refactor planning, performance review.
- Depth: quick, standard, or deep explanation.
If user gives no scope, default to project-level explanation.
Analysis Workflow
Follow this order:
- Project map
- Identify main folders and responsibilities.
- Summarize app entry points and bootstrapping.
- Architecture
- Determine architecture style (layered, feature-first, mixed).
- Map core boundaries: presentation, domain/logic, data, shared/core.
- State management
- Identify state solution(s): Riverpod, Bloc/Cubit, GetX, Provider, setState, others.
- Explain where each is used and why.
- Flag inconsistent or mixed usage hotspots.
- Navigation and app flow
- Explain routing setup and screen transitions.
- Summarize primary user journey paths.
- Data flow and integrations
- Trace data path from UI event to repository/service and back.
- Explain API clients, DTO/model mapping, caching, and persistence.
- Note authentication and push integration points if present.
- Dependencies and cross-cutting concerns
- Highlight important packages and what each is used for.
- Explain logging, error handling, dependency injection, config/env handling.
- Quality and risks
- Identify likely tech debt areas, coupling, duplication, and test gaps.
- Identify potential runtime-risk points (null handling, async race, network assumptions).
- Actionable next steps
- Provide prioritized recommendations (high impact first).
- Include low-risk quick wins and medium-term refactors.
Output Format
Return explanation in this structure:
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.
- 3d ago First seen · 96 lines · 41 tokens per session scan A 3eb23f6b844e
flutter-explain-codebase is a skill published in the GitHub repository mdazadhossain95/flutter-agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 702 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.
Other skills, from other repositories
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
react-native-ease-refactor
Scan for Animated/Reanimated code and migrate to EaseView.
app_remix
Create a new Rome app from an App Store source, already installed or identified by a pinned Store version. Copy installed code locally or download and extract a Store bundle without installing the source. Never edit or overwrite an existing source app.