Borrowing it
Nothing to install: this file belongs to flutter/dart-intellij-third-party. 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/flutter/dart-intellij-third-party/main/.agents/skills/monthly-release/SKILL.mdgit clone --depth 1 https://github.com/flutter/dart-intellij-third-partyWrote 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/flutter/dart-intellij-third-party/monthly-release)<a href="https://agentmods.dev/skills/flutter/dart-intellij-third-party/monthly-release"><img src="https://agentmods.dev/badge/skills/flutter/dart-intellij-third-party/monthly-release/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/flutter/dart-intellij-third-party/monthly-release"><img src="https://agentmods.dev/badge/skills/flutter/dart-intellij-third-party/monthly-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 33 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00018 | $0.01016 |
| Opus 5 | $0.00009 | $0.00508 |
| Sonnet 5 | $0.00004 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
monthly-release 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monthly Plugin Release Process
Use this skill when preparing, testing, validating, and publishing a new monthly release of the Dart IntelliJ plugin (dart-intellij-third-party).
[!NOTE] Platform Compatibility Policy:
untilBuildis intentionally omitted ingradle.propertiesandbuild.gradle.ktsto maintain open-ended compatibility with future IDE builds without artificial version caps. Do NOT adduntilBuildcaps during monthly releases.
Release Process Checklist
1. Update Changelog for the Release
- Branch:
changelog(created offupstream/main) - Goal: Collect unreleased user-facing PRs into the release version header and set up a new
## Unreleasedblock. - Steps:
- Review commits merged since the previous release (
git log <last-release-commit>..upstream/main). - Identify missing user-facing PRs (bug fixes, new features, performance enhancements).
- In
third_party/CHANGELOG.md, rename## Unreleasedto## <new-version>(e.g.## 508.0.0). - Follow changelog formatting conventions:
- Entries must strictly use descriptive, state-based phrases (typically starting with gerunds, nouns, or verbs like Avoid / Support / Log / Prevent) rather than starting with imperative verbs like Fix or Add.
- Under
### Removed, do NOT repeat action verbs like "Remove" (e.g.,- untilBuild restriction (#553)).
- Add a fresh empty
## Unreleasedsection at the top ofthird_party/CHANGELOG.mdwith standard subheaders (### Added,### Changed,### Removed,### Fixed). - Create PR (e.g.
Update changelog for <version> (#<PR>)) and merge it tomain. - Delete local and remote
changelogbranch upon merge (git branch -D changelog).
- Review commits merged since the previous release (
2. Build & Validate
- Compilation & Structure Verification:
- Ensure local
mainis checked out and updated (git fetch upstream && git checkout main && git reset --hard upstream/main), and navigate to thethird_partydirectory (cd third_party). - Run compilation check:
./gradlew testClasses - Run plugin structure validation:
./gradlew verifyPluginStructure - Run unit tests:
./gradlew test
- Ensure local
- Build Prospective Release Zip Artifact:
- Run the Gradle build with
-PversionedName(from thethird_partydirectory):./gradlew buildPlugin -PversionedName - Behavior:
- Gradle reads the release version (
<version>) directly fromCHANGELOG.md. - The
-PversionedNameflag instructsbuild.gradle.ktsto outputDart-<version>-<commitHash>.zip. - Generated zip location:
third_party/build/distributions/Dart-<version>-<commitHash>.zip.
- Gradle reads the release version (
- Run the Gradle build with
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 · 69 lines · 18 tokens per session scan A 35ffc0fe7a00
monthly-release is a skill published in the GitHub repository flutter/dart-intellij-third-party (25 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 18 tokens to every session and 1,016 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 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.
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.
updater_guide
Guidance for checking for and installing Row-Bot updates.