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 commands/aaronbassett/agent-foundry/flutter-upgradegit clone --depth 1 https://github.com/aaronbassett/agent-foundryWrote 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/aaronbassett/agent-foundry/flutter-upgrade)<a href="https://agentmods.dev/commands/aaronbassett/agent-foundry/flutter-upgrade"><img src="https://agentmods.dev/badge/commands/aaronbassett/agent-foundry/flutter-upgrade.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.00018 | $0.02453 |
| Opus 5 | $0.00009 | $0.01226 |
| Sonnet 5 | $0.00004 | $0.00491 |
| Haiku 4.5 | $0.00002 | $0.00245 |
Grade A, and why
flutter-upgrade 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.
How it starts
The opening of the file, as written. The whole thing — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Upgrade Manager
This command manages Flutter SDK and dependency upgrades, detects breaking changes, applies migrations, and ensures smooth version transitions.
Usage
/flutter-upgrade [target] [options]
Targets
sdk- Upgrade Flutter SDK onlydeps- Upgrade project dependencies onlyall- Upgrade both SDK and dependencies (default)
Options
--check-only- Check for available upgrades without applying--migrate- Run migration tools after upgrade--major- Allow major version upgrades (default: minor only)--force- Skip confirmation prompts
Examples
# Check what's available
/flutter-upgrade --check-only
# Upgrade SDK only
/flutter-upgrade sdk
# Upgrade dependencies with migration
/flutter-upgrade deps --migrate
# Complete upgrade with major versions
/flutter-upgrade all --major --migrate
# Force upgrade without prompts
/flutter-upgrade --force
Implementation
When this command runs:
1. Environment Check
Verify Flutter installation:
flutter --version
flutter doctor -v
Check current project:
# Verify pubspec.yaml exists
if [ ! -f "pubspec.yaml" ]; then
echo "Error: Not a Flutter project"
exit 1
fi
# Save current versions for rollback
cp pubspec.yaml pubspec.yaml.backup
flutter --version > .flutter_version_backup
2. Check for Updates
SDK Updates:
# Check Flutter channel
flutter channel
# Check for SDK updates
flutter upgrade --dry-run
Parse output to identify:
- Current SDK version
- Available SDK version
- Breaking changes between versions
Dependency Updates:
# Check for outdated packages
flutter pub outdated --mode=null-safety
Parse output for:
- Current versions
- Latest compatible versions
- Latest versions (may require major upgrade)
3. Present Upgrade Plan
Show user what will be upgraded:
Flutter Upgrade Plan
====================
SDK Upgrade:
Current: Flutter 3.16.5 • Dart 3.2.3
Available: Flutter 3.19.0 • Dart 3.3.0
Breaking Changes:
- Material 3 is now default
- ThemeData.useMaterial3 defaults to true
- Deprecated APIs removed: Scaffold.resizeToAvoidBottomPadding
Dependency Upgrades:
provider: 6.0.5 → 6.1.2 (minor)
http: 0.13.6 → 1.2.0 (major) ⚠️
Breaking: Response.body now Future<String>
dio: 5.3.3 → 5.4.1 (minor)
flutter_bloc: 8.1.3 → 8.1.5 (patch)
Test Dependencies:
mockito: 5.4.2 → 5.4.4 (patch)
Recommendations:
1. Review http 1.x migration guide
2. Test thoroughly after Material 3 upgrade
3. Run tests before and after upgrade
Continue? (y/n)
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.
- 5d ago First seen · 463 lines · 18 tokens per session scan A 6fca07fcd043
flutter-upgrade is a command published in the GitHub repository aaronbassett/agent-foundry (4 stars, last pushed 20d ago), licensed MIT. It adds 18 tokens to every session and 2,453 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-31.
Other commands, from other repositories
compose-test
Run Compose UI tests with Espresso. Verify critical user flows.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
ios-privacy
Prepare privacy labels, permissions, policy links, and data-use truth for iOS release.
maestro-selectors-instructions
Guide to using Maestro selectors for targeting UI elements in tests.
initialize-ios
Manual override: initialize ast-index for iOS/Swift/ObjC project.
mobile-performance-check
Analyze mobile app for performance issues using the mobile-best-practices database.