Borrowing it
Nothing to install: this file belongs to Kandil7/prprompts-flutter-generator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Kandil7/prprompts-flutter-generator/master/.claude/commands/planning/analyze-dependencies.mdgit clone --depth 1 https://github.com/Kandil7/prprompts-flutter-generatorWrote 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/commands/kandil7/prprompts-flutter-generator/analyze-dependencies)<a href="https://agentmods.dev/commands/kandil7/prprompts-flutter-generator/analyze-dependencies"><img src="https://agentmods.dev/badge/commands/kandil7/prprompts-flutter-generator/analyze-dependencies/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.
<a href="https://agentmods.dev/commands/kandil7/prprompts-flutter-generator/analyze-dependencies"><img src="https://agentmods.dev/badge/commands/kandil7/prprompts-flutter-generator/analyze-dependencies.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00012 | $0.04729 |
| Opus 5 | $0.00006 | $0.02364 |
| Sonnet 5 | $0.00002 | $0.00946 |
| Haiku 4.5 | $0.00001 | $0.00473 |
Grade A, and why
Analyze Feature Dependencies 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.
How it starts
The opening of the file, as written. The whole thing — 636 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Dependency Analysis
Overview
Analyze PRD features to identify dependencies, blockers, and parallel work opportunities. Generate implementation order recommendations with critical path analysis.
Instructions
Step 1: Locate and Read PRD
# Expected location
docs/PRD.md
If not found, ask user for PRD location.
Step 2: Extract Features
Parse YAML frontmatter features array:
features:
- name: "User Authentication"
complexity: "medium"
priority: "p0"
requires: ["biometric_auth", "mfa"]
- name: "Dashboard"
complexity: "medium"
priority: "p0"
requires: ["real_time_updates", "data_visualization"]
Also extract from PRD body if features have expanded descriptions with:
- User stories
- Technical requirements
- Acceptance criteria
Step 3: Identify Dependency Types
1. Technical Dependencies (BLOCKING) These MUST be implemented first:
-
Authentication → All Features:
- Any feature requiring user identity depends on auth
- Keywords: "user-specific", "personalized", "profile", "account"
-
Database Schema → CRUD Features:
- Data models must exist before features using them
- Keywords: "save", "retrieve", "update", "delete", "store"
-
API Foundation → API-Dependent Features:
- Backend endpoints required before frontend consumption
- Keywords: "fetch from server", "API call", "REST endpoint"
-
Payment Integration → Monetization:
- Stripe/PayPal setup blocks checkout, subscriptions, billing
- Keywords: "payment", "checkout", "billing", "subscription"
-
Search Infrastructure → Search Features:
- Elasticsearch/Algolia needed before search UI
- Keywords: "search", "find", "filter", "query"
2. Logical Dependencies (STRONGLY RECOMMENDED) Should be implemented in order, but can be worked around:
-
Core Entity → Related Entities:
- Example: "Product" before "Product Reviews"
- Example: "User Profile" before "User Preferences"
-
Create → Read/Update/Delete:
- Must be able to create entities before managing them
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 · 636 lines · 12 tokens per session scan A 53d83bfd72b0
Analyze Feature Dependencies is a command published in the GitHub repository Kandil7/prprompts-flutter-generator (11 stars, last pushed 9mo ago), licensed MIT. It adds 12 tokens to every session and 4,729 once invoked, about $0.0001 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.
Other commands, from other repositories
building-flutter-apps-skill-ac1294fc
Flutter Riverpod app architecture and Windows installer delivery. Use before changing a Riverpod Flutter app/package or its Windows desktop packaging/update pipeline; skip non-Riverpod stacks and pure-Dart work.
gdpr-audit
You are a senior Security & Compliance specialist. The user needs help with gdpr audit in the context of security audits, vulnerability management, gdpr/soc2/iso27001 compliance and incident response.
privacy-policy
You are a senior Security & Compliance specialist. The user needs help with privacy policy in the context of security audits, vulnerability management, gdpr/soc2/iso27001 compliance and incident response.
secret-detect
You are a senior Security & Compliance specialist. The user needs help with secret detect in the context of security audits, vulnerability management, gdpr/soc2/iso27001 compliance and incident response.
threat-model
You are a senior Security & Compliance specialist. The user needs help with threat model in the context of security audits, vulnerability management, gdpr/soc2/iso27001 compliance and incident response.
dep-cve
You are a senior Security & Compliance specialist. The user needs help with dep cve in the context of security audits, vulnerability management, gdpr/soc2/iso27001 compliance and incident response.