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/devoncarew/flutter-slipstream/add-packagenpx skills add devoncarew/flutter-slipstream --skill add-packagegit clone --depth 1 https://github.com/devoncarew/flutter-slipstreamWhat 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.00074 | $0.00526 |
| Opus 5 | $0.00037 | $0.00263 |
| Sonnet 5 | $0.00015 | $0.00105 |
| Haiku 4.5 | $0.00007 | $0.00053 |
Grade A, and why
add-package 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 2d 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.
What it actually says
Adding a Dart/Flutter Package Dependency
Preferred approach
Use flutter pub add <package> (or dart pub add) rather than editing
pubspec.yaml directly. The pub command output is the primary signal for
package health; direct edits bypass it.
Read pub output after every add
After running pub add, read the output carefully before proceeding. Two
classes of problem appear inline:
Discontinued packages
+ flutter_markdown 0.7.7+1 (discontinued replaced by flutter_markdown_plus)
...
1 package is discontinued.
Action:
- If a replacement is listed: remove the discontinued package and add the
replacement instead (
flutter pub remove <pkg>thenflutter pub add <replacement>). - If no replacement is listed: find a well-maintained alternative before proceeding.
Version pinned behind current major
+ lints 4.0.0 (6.1.0 available)
...
4 packages have newer versions incompatible with dependency constraints.
The (X.Y.Z available) annotation on a package you just added means the version
you requested is behind the current release — often by a major version.
Action:
-
Run
flutter pub outdatedto see the structured breakdown:Package Name Current Upgradable Resolvable Latest lints *4.0.0 *4.0.0 6.1.0 6.1.0 -
If a direct dependency you just added shows a major-version gap between Current and Latest, remove the version pin or update the constraint to the current major (
flutter pub add 'lints:^6.0.0'). -
Transitive dependency gaps are generally not actionable — note them but don't block on them.
When editing pubspec.yaml directly
If you add a dependency by editing pubspec.yaml instead of using pub add,
run flutter pub get immediately after and apply the same output-reading rules.
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.
- 2d ago First seen · 71 lines · 74 tokens per session scan A 3c423b2062e7
add-package is a skill published in the GitHub repository devoncarew/flutter-slipstream (5 stars, last pushed 15d ago), licensed BSD-3-Clause. It adds 74 tokens to every session and 526 once invoked, about $0.0004 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
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
schema-markup-generator
Generate JSON-LD structured data markup for rich results in Google Search. Supports FAQ, HowTo, Article, Product, LocalBusiness, and multi-type schemas. Validates against Google requirements and provides implementation guidance. Use when asked to "add schema markup", "generate structured data", "JSON-LD", "rich…
shopify-hydrogen
Hydrogen storefront implementation cookbooks. Some of the available recipes are: B2B Commerce, Bundles, Combined Listings, Custom Cart Method, Dynamic Content with Metaobjects, Express Server, Google Tag Manager Integration, Infinite Scroll, Legacy Customer Account Flow, Markets, Partytown + Google Tag Manager…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sitemap-audit
XML sitemap audit — find and fix the sitemap problems that quietly waste crawl budget and slow indexing. Discovers the sitemap (robots.txt, /sitemap.xml, sitemap index), validates structure and size limits, and cross-checks the URLs it lists against reality: non-200 / redirected / noindex / canonicalized-away URLs…
paid-ads-linkedin
Audit, diagnose, plan, and safely operate connected LinkedIn Ads accounts through the NotFair MCP, with an export-based fallback. Use for LinkedIn advertising, sponsored content, lead-generation forms, job-title or company targeting, campaign groups, creatives, conversions, lead quality, budgets, bids, or approved…