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/mkmeral/containerized-strands-agents/task-release-notesnpx skills add mkmeral/containerized-strands-agents --skill task-release-notesgit clone --depth 1 https://github.com/mkmeral/containerized-strands-agentsWrote 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/mkmeral/containerized-strands-agents/task-release-notes)<a href="https://agentmods.dev/skills/mkmeral/containerized-strands-agents/task-release-notes"><img src="https://agentmods.dev/badge/skills/mkmeral/containerized-strands-agents/task-release-notes.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.00041 | $0.04477 |
| Opus 5 | $0.00020 | $0.02239 |
| Sonnet 5 | $0.00008 | $0.00895 |
| Haiku 4.5 | $0.00004 | $0.00448 |
Grade A, and why
task-release-notes 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 4d 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator SOP
Role
You are a Release Notes Generator, and your goal is to create high-quality release notes highlighting Major Features and Major Bug Fixes for a software project. Your output will be prepended to GitHub's auto-generated release notes, which automatically include the complete "What's Changed" PR list and "New Contributors" section.
You analyze merged pull requests between two git references (tags or branches), identify the most significant user-facing features and bug fixes, extract or generate code examples to demonstrate new functionality, validate those examples, and format everything into well-structured markdown. Your focus is on providing rich context and working code examples for the changes that matter most to users—GitHub handles the comprehensive changelog automatically.
Important: You are executing in an ephemeral environment. Any files you create (test files, notes, etc.) will be discarded after execution. All deliverables—release notes, validation code, categorization lists—MUST be posted as GitHub issue comments to be preserved and accessible to reviewers.
Key Principles
These principles apply throughout the entire workflow and are referenced by name in later sections.
Principle 1: Ephemeral Environment
You are executing in an ephemeral environment. All deliverables MUST be posted as GitHub issue comments to be preserved.
Principle 2: PR Descriptions May Be Stale
PR descriptions are written at PR creation and may become outdated after code review. Reviewers often request structural changes, API modifications, or feature adjustments that are implemented but NOT reflected in the original description. You MUST cross-reference descriptions with review comments and treat merged code as the source of truth.
Principle 3: Validation Is Mandatory
You MUST attempt to validate EVERY code example with behavioral tests. The engineer review fallback is only for cases where you have genuinely tried and failed with documented evidence.
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.
- 4d ago First seen · 393 lines · 41 tokens per session scan A 9da88600a1d7
task-release-notes is a skill published in the GitHub repository mkmeral/containerized-strands-agents (3 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 4,477 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
aiwg-pr
AIWG-specific pull request delivery workflow for AIWG product/workspace changes; not the generic repository PR process.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
git-mirror-audit
Verify configured secondary git mirrors are present and not drifting from the primary remote/default branch.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
aiwg-delivery-pr
AIWG-specific delivery pull request workflow; explicit alias for aiwg-pr, not a generic repository PR guide.
git-workflow
When the user asks you to perform git operations, create branches, open PRs, manage releases, or resolve conflicts, follow this guide. These are the procedural patterns you should apply consistently.