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 koaning/wigglystuff --skill prep-releasegit clone --depth 1 https://github.com/koaning/wigglystuffWrote 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/koaning/wigglystuff/prep-release)<a href="https://agentmods.dev/skills/koaning/wigglystuff/prep-release"><img src="https://agentmods.dev/badge/skills/koaning/wigglystuff/prep-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/koaning/wigglystuff/prep-release"><img src="https://agentmods.dev/badge/skills/koaning/wigglystuff/prep-release.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.00000 | $0.00910 |
| Opus 5.5 | $0.00000 | $0.00364 |
| Sonnet 5.5 | $0.00000 | $0.00182 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
prep-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 yesterday.
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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Preparation
Prepare a new wigglystuff release. Follow these steps:
Instructions
-
Determine the new version: Read
pyproject.tomlfor the current version and the latest entry inCHANGELOG.md. If the version has already been bumped, use that. Otherwise, bump the patch version (e.g., 0.2.24 -> 0.2.25). -
Bump version in
pyproject.toml(if not already done). -
Add a changelog entry at the top of
CHANGELOG.mdfollowing the existing format:- Use
## [x.y.z] - YYYY-MM-DDheader with today's date - Add
### Added,### Changed,### Fixed, or### Removedsubsections as appropriate - Look at the git diff against
mainto determine what changed
- Use
-
Update all documentation locations for any new widgets:
docs/reference/<widget-name>.md— create a reference doc following the pattern in existing reference pages (use::: wigglystuff.module.ClassNamemkdocstrings directive + a synced traitlets table)zensical.toml— add the widget to thenavReference sectiondocs/index.md— add to the appropriate gallery section (main gallery or 3rd party gallery)readme.md— add to the appropriate gallery table (main gallery or 3rd party table)docs/llms.txt— add a one-line entry in the appropriate sectionCLAUDE.md— add a row to the quick reference tablewigglystuff/__init__.py— verify the widget is imported and listed in__all__
-
For 3rd party widgets (those requiring non-core dependencies like neo4j, torch, wandb):
- Place them in the "3rd party widgets" section of the galleries (not the main gallery)
- Use a molab link for the demo instead of a local example page
- Use
MOLAB_LINK_HEREas a placeholder if the molab link is not yet available and tell the user they need to fill it in - Screenshot path should be
docs/assets/gallery/<widgetname>.webp— tell the user if one is missing (runuv run python scripts/png_to_webp.pyif a PNG was added)
-
Check dependencies: Read
pyproject.tomland verify that no 3rd party widget dependency (neo4j, torch, wandb, etc.) has been added to core[project] dependencies. These must only appear under[project.optional-dependencies]as extras. Core dependencies should only include packages needed by all widgets (anywidget, numpy, pillow, python-dotenv). If a 3rd party dep has leaked into core dependencies, remove it.
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.
- yesterday First seen · 40 lines · 0 tokens per session scan A 7c140e7cd566
prep-release is a skill published in the GitHub repository koaning/wigglystuff (450 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 910 tokens. 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-10-14.
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.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
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.