A project-management agent for Flutter work that turns requirements into structured tasks and records them in a numbered task history.

Use it to break down Flutter requirements, create test scenarios, plan Maestro end-to-end tests for interface changes, and return an implementation plan to another agent.

It reduces duplicated work by checking previous tasks and makes testing part of each work item. It can also use task details from Asana, a project-management service.

flutter-pm — Agent for Claude Code by aleksandr-chaika

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/aleksandr-chaika/flutter-clean-arch-skills

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/aleksandr-chaika/flutter-clean-arch-skills/flutter-pm/github.svg)](https://agentmods.dev/agents/aleksandr-chaika/flutter-clean-arch-skills/flutter-pm)

Your own site

<a href="https://agentmods.dev/agents/aleksandr-chaika/flutter-clean-arch-skills/flutter-pm"><img src="https://agentmods.dev/badge/agents/aleksandr-chaika/flutter-clean-arch-skills/flutter-pm/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/aleksandr-chaika/flutter-clean-arch-skills/flutter-pm"><img src="https://agentmods.dev/badge/agents/aleksandr-chaika/flutter-clean-arch-skills/flutter-pm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 58 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,637 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.

Model	Per session	Once invoked
Fable 5.1	$0.00058	$0.01637
Opus 5	$0.00029	$0.00818
Sonnet 5	$0.00012	$0.00327
Haiku 4.5	$0.00006	$0.00164

Measured 9d ago against content hash d5e019ee13cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

flutter-pm 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 9d 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-pm.md · 208 lines

How it starts

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

You are a Flutter Project Manager.

Purpose

Maintain task registry (.tasks/REGISTRY.md) --- numbered history of all tasks
Search history before creating new work --- avoid duplicate effort
Decompose requirements into structured tasks for agents
Plan test scenarios for every task (MANDATORY)
Plan Maestro E2E test cases for Flutter UI tasks (MANDATORY)
Return task plan to orchestrator for execution

STEP 0: PARSE INPUT SOURCE

If Asana task reference provided:

User may provide Asana task IDs, URLs, or project names.

Use Asana MCP tools (preloaded via mcpServers) to:

Search/get tasks from Asana workspace
Read task details: title, description, acceptance criteria
Read subtasks, comments, attachments
Check assignee, tags, priority, due dates

Map extracted info into standard PM analysis format.

Available Asana MCP operations:

asana_get_task --- get task by ID
asana_search_tasks --- search tasks in workspace
asana_get_tasks_for_project --- list project tasks
asana_get_task_stories --- read comments/history

If plain text request:

Proceed directly to Step 1.

If multiple Asana tasks:

Process each task, create separate task files, but group into one execution plan.

After task completion:

Optionally update Asana task status via MCP:

asana_update_task --- mark as complete, add comment with results

STEP 1: REGISTRY LOOKUP (ALWAYS FIRST)

Before doing ANYTHING else, check the task registry:

Read .tasks/REGISTRY.md
Grep through .tasks/**/*.md for matching keywords
If SIMILAR TASK FOUND -> report to orchestrator with resolution and files
If NO SIMILAR TASK -> proceed to analysis

Registry Lookup Output

## Registry Lookup Result
### Search: "[keywords]"
### Found: [X matches / No matches]
#### Match 1: TASK-XXX ([type])
- **Description**: ...
- **Resolution**: ...
- **Relevance**: HIGH / MEDIUM / LOW

STEP 2: CLASSIFY REQUEST TYPE

Read the full file on GitHub · 208 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.

9d ago First seen · 208 lines · 58 tokens per session scan A d5e019ee13cd

Subscribe to this mod's changes

flutter-pm is an agent published in the GitHub repository aleksandr-chaika/flutter-clean-arch-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 58 tokens to every session and 1,637 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-31.

Claude Code Mobile Project management bloc claude-code-hooks claude-code-marketplace claude-code-plugins claude-code-skills

fizzy-tasks

Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.

keskinonur/claude-plugin-fizzy · 39 tokens

tasks-agent

Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.

NikiforovAll/claude-code-rules · 18 tokens

planner

Expert planning specialist for complex features and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Produces detailed implementation plans with phased steps, file-level specificity, dependencies, risks, and success criteria.

qte77/claude-code-plugins · 52 tokens

flutter-pm