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/blocunited-llc/mozaiks/release-notesnpx skills add BlocUnited-LLC/mozaiks --skill release-notesgit clone --depth 1 https://github.com/BlocUnited-LLC/mozaiksWrote 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/blocunited-llc/mozaiks/release-notes)<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/release-notes"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/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.00054 | $0.00470 |
| Opus 5 | $0.00027 | $0.00235 |
| Sonnet 5 | $0.00011 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
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.
What it actually says
Before starting: git fetch origin && gh pr list --state open && git log origin/main --oneline -3 — if another agent has an open PR touching the same files you need, wait for it to merge or branch off it instead of main.
Complete this release-notes task: $ARGUMENTS
Goal
Keep OSS Mozaiks release notes accurate without waiting until release day.
When To Update CHANGELOG.md
Add an Unreleased entry when a change affects:
- CLI behavior or command output
- generated app scaffolds, scripts, or templates
- runtime, workflow, module, shell, event, or extension contracts
- packaging, PyPI, install, launch, or release CI behavior
- public docs that change how users install, run, or build with Mozaiks
- bug fixes or migration notes users would care about
Skip changelog entries for purely internal refactors, tests with no behavior change, or small editorial fixes that do not affect user workflow.
Entry Style
Use one concise bullet under the right section:
AddedChangedFixedRemovedSecurity
Write from the user's point of view. Prefer:
- "Added generated app launch scripts for backend, frontend, and Studio."
Avoid:
- "Refactored helper function and changed three files."
Release Prep Checklist
Before tagging:
- confirm all release-impacting work is listed under
Unreleased - move entries to
## <version> - <YYYY-MM-DD> - create a fresh empty
## Unreleasedsection - verify
mozaiksai/version.pymatches the tag - copy or summarize that version section into the GitHub Release notes
Keep private hosted-product release notes separate from this OSS framework changelog unless the change is in this repo and affects public Mozaiks users.
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 · 61 lines · 54 tokens per session scan A fe01410c43ed
release-notes is a skill published in the GitHub repository BlocUnited-LLC/mozaiks (25 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 470 once invoked, about $0.0003 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
add-new-model
Add support for a newly-released LLM model in pydantic-ai (e.g. openai:gpt-5.6, anthropic:claude-sonnet-5). Use when a provider ships a new model id and you need to wire literals, profile flags, and tests to recognize it. Handles SDK-lag, gateway list conventions, and capability probing.
building-pydantic-ai-agents
Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydanticai, or asks to build an AI agent, add tools/capabilities, defer capability loading, stream output, define agents…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
testing-skill
Record, rewrite, and debug VCR cassettes for HTTP recordings. Use when running tests with --record-mode, verifying cassette playback, or inspecting request/response bodies in YAML cassettes.
pre-push-review
Run a high-judgment local review of the current branch before pushing, both before a PR exists and between PR iterations.
adding-a-provider-api-feature
Add a new provider API capability (prompt caching, strict/structured tool calling, thinking/reasoning effort, service tier, safety settings, logprobs, etc.) to Pydantic AI. Use when wiring a provider feature through the library — it enforces reasoning from the existing cross-provider abstraction before designing…