What is dart-package-maintenance?

A maintenance guide for external Dart packages, covering version numbers, changelogs, releases, and pull requests. It explains semantic versioning, where major, minor, and patch changes communicate the size of an update.

Use it when updating, versioning, publishing, or reviewing changes to a Dart package.

It helps prevent changelog and package-version mistakes, especially when preparing a release or changing an already published package.

dart-package-maintenance — Skill for Claude Code and Codex by kevmoo

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.

Any agent

npx skills add kevmoo/dash_skills --skill dart-package-maintenance

Clone the repo

git clone --depth 1 https://github.com/kevmoo/dash_skills

Made for: Claude Code, Codex.

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/skills/kevmoo/dash_skills/dart-package-maintenance/github.svg)](https://agentmods.dev/skills/kevmoo/dash_skills/dart-package-maintenance)

Your own site

<a href="https://agentmods.dev/skills/kevmoo/dash_skills/dart-package-maintenance"><img src="https://agentmods.dev/badge/skills/kevmoo/dash_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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/kevmoo/dash_skills/dart-package-maintenance"><img src="https://agentmods.dev/badge/skills/kevmoo/dash_skills/dart-package-maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 977 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00047	$0.00977
Opus 5	$0.00023	$0.00489
Sonnet 5	$0.00009	$0.00195
Haiku 4.5	$0.00005	$0.00098

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

Security

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.

skills/dart-package-maintenance/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 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.

Discovery

To find maintenance tasks or inconsistencies:

Consistency Checks

Ensure the latest version in CHANGELOG.md matches pubspec.yaml:

Compare the top header in CHANGELOG.md with the version: field in pubspec.yaml.

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.0 as soon as the package is stable.

Pre-Edit Verification

Check Published Versions: Before modifying CHANGELOG.md or pubspec.yaml, ALWAYS check the currently released version (e.g., via git tag or pub.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.yaml matches a released tag, increment the version (e.g., usually to -wip) and create a new section in CHANGELOG.md.
- Consistency: The CHANGELOG.md header must match the new pubspec.yaml version.
- 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).

Changelog Content

Focus on User Impact: Entries in CHANGELOG.md should focus on changes visible to or impacting the end-user (e.g., new features, bug fixes, breaking changes).
Omit Internal Changes: Do not include internal refactorings, test changes, or other modifications that do not affect the package's behavior or API for the user.

Work-in-Progress (WIP) Versions

Immediately after a publish, or on the first change after a publish, update pubspec.yaml and CHANGELOG.md with a -wip suffix (e.g., 1.1.0-wip).
This indicates the current state is not yet published.

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

10d ago First seen · 97 lines · 47 tokens per session scan A e79492437d2f

Subscribe to this mod's changes

dart-package-maintenance is a skill published in the GitHub repository kevmoo/dash_skills (144 stars, last pushed 2d ago), licensed Apache-2.0. It adds 47 tokens to every session and 977 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-30.

Git and workflow Kotlin and Swift Languages Releases agent-skills

release-kotlin-library

Use when preparing, publishing, or checking readiness for a new Kotlin library version in a repository using gradle-maven-publish-plugin, including release changelog reconciliation, API snapshots, and publication verification.

chrisbanes/skills · 45 tokens

kmp-library-publishing

Publish a Kotlin Multiplatform library to Maven Central, GitHub Packages, or both. Covers: vanniktech maven-publish plugin setup, POM metadata, Sonatype OSSRH staging, multi-artifact BOM, kotlinx-binary-compatibility-validator API tracking, SNAPSHOT vs stable channels, and a release checklist. Pairs with…

ronjunevaldoz/kmp-agent-skills · 89 tokens

toggle-sibling-libraries

Toggle a Swift Package.swift between the local-sibling-checkout development pattern and a clean remote-only release pattern. Use this skill whenever you need to flip Package.swift in or out of the sibling(...) helper-function pattern — for example, before tagging a release the dependencies must be pinned to…

intrusive-memory/skills · 162 tokens

dart-package-maintenance