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 skills add mdazadhossain95/flutter-agent-skills --skill dart-package-maintenancegit 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/dart-package-maintenance)<a href="https://agentmods.dev/skills/mdazadhossain95/flutter-agent-skills/dart-package-maintenance"><img src="https://agentmods.dev/badge/skills/mdazadhossain95/flutter-agent-skills/dart-package-maintenance/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/skills/mdazadhossain95/flutter-agent-skills/dart-package-maintenance"><img src="https://agentmods.dev/badge/skills/mdazadhossain95/flutter-agent-skills/dart-package-maintenance.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.00047 | $0.00808 |
| Opus 5 | $0.00023 | $0.00404 |
| Sonnet 5 | $0.00009 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
dart-package-maintenance 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 10d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dart Package Maintenance
Guidelines for maintaining Dart packages in alignment with Dart team best practices.
Versioning
Semantic Versioning
- Major: Breaking changes.
- Minor: New features (non-breaking API changes).
- Patch: Bug fixes, documentation, or non-impacting changes.
- Unstable packages: Use
0.major.minor+patch. - Recommendation: Aim for
1.0.0as soon as the package is stable.
Pre-Edit Verification
-
Check Published Versions: Before modifying
CHANGELOG.mdorpubspec.yaml, ALWAYS check the currently released version (e.g., viagit tagorpub.dev). -
Do Not Amend Released Versions: Never add new entries to a version header that corresponds to a released tag.
-
Increment for New Changes: If the current version in
pubspec.yamlmatches a released tag, increment the version (e.g., usually to-wip) and create a new section inCHANGELOG.md.-
Consistency: The
CHANGELOG.mdheader must match the newpubspec.yamlversion. -
SemVer Guidelines:
- Breaking Changes: Bump Major, reset Minor/Patch
(e.g.,
2.0.0-wip,0.5.0-wip). - New Features: Bump Minor, reset Patch
(e.g.,
1.1.0-wip,0.4.5-wip). - Bug Fixes: Bump Patch (e.g.,
1.0.1-wip).
- Breaking Changes: Bump Major, reset Minor/Patch
(e.g.,
-
Work-in-Progress (WIP) Versions
- Immediately after a publish, or on the first change after a publish, update
pubspec.yamlandCHANGELOG.mdwith a-wipsuffix (e.g.,1.1.0-wip). - This indicates the current state is not yet published.
Breaking Changes
- Evaluate the impact on dependent packages and internal projects.
- Consider running changes through internal presubmits if possible.
- Prefer incremental rollouts (e.g., new behavior as opt-in) to minimize downstream breakage.
Publishing Process
- Preparation: Remove the
-wipsuffix frompubspec.yamlandCHANGELOG.mdin a dedicated pull request. - Execution: Run
dart pub publish(orflutter pub publish) and resolve all warnings and errors. - Tagging: Create and push a git tag for the published version:
- For single-package repos:
v1.2.3 - For monorepos:
package_name-v1.2.3 - Example:
git tag v1.2.3 && git push --tags
- For single-package repos:
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.
- 10d ago First seen · 76 lines · 47 tokens per session scan A 5162038f5455
dart-package-maintenance is a skill published in the GitHub repository mdazadhossain95/flutter-agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 808 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.