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 white1024/agent-nextup --skill ship-notesgit clone --depth 1 https://github.com/white1024/agent-nextupWrote 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/white1024/agent-nextup/ship-notes)<a href="https://agentmods.dev/skills/white1024/agent-nextup/ship-notes"><img src="https://agentmods.dev/badge/skills/white1024/agent-nextup/ship-notes/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/white1024/agent-nextup/ship-notes"><img src="https://agentmods.dev/badge/skills/white1024/agent-nextup/ship-notes.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.00062 | $0.00818 |
| Opus 5.5 | $0.00025 | $0.00327 |
| Sonnet 5.5 | $0.00012 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
ship-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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ship-notes — what changed, how we know, can it be undone
Goal: someone who was not in the session can decide from this page alone whether to take the change and how carefully.
In a Release phase the file is artifacts/release-notes.md — the phase's exit gate checks that it exists. The same shape works as a PR body. Use the project's own vocabulary (GLOSSARY.md if there is one) and skip the preamble.
The shape
## Summary
<the smallest picture that makes the change clear>
## Evidence
- **Before:** <failing test run, output or screenshot>
**After:** <passing run, output or screenshot>
## Can it be undone?
**Door:** one-way | two-way
**Reach:** <one word — what it can affect>
<only if needed: what could go wrong, and how to roll back>
## Known limitations and follow-ups
Summary: pick the smallest picture
One or two of these, placed next to the sentence they support — never all of them:
- Pseudocode for logic or an algorithm.
- A call tree for runtime control flow.
- A component tree for UI structure, with the state and boundaries that matter.
- A shallow file tree for responsibilities or a broad refactor.
- A sequence diagram (Mermaid) for interactions between parts.
- A diff of any of the above when the point is what changed and the surrounding shape already exists.
Evidence
Show the change working, before and after. A screenshot is the best evidence for a visual change; a test run or real output is next — name the test that failed before and passes now. "Tests pass" with nothing shown is not evidence.
Can it be undone
A two-way door can be walked back cheaply: revert and nothing is lost. A one-way door cannot: a migration, a deleted field, a changed contract others depend on, anything destructive. Say which, then give the reach in a word — layout, consumers, data, performance — and the ramifications if it is one-way.
Adapted from pr in mattpocock/skills, itself crediting show-me by Dex Horthy (HumanLayer), and rewired to Agent NextUp's engine. The original is distributed under this licence:
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 · 77 lines · 62 tokens per session scan A 98421b20d3f4
ship-notes is a skill published in the GitHub repository white1024/agent-nextup (2 stars, last pushed 5d ago), licensed MIT. It adds 62 tokens to every session and 818 once invoked, about $0.0002 per session on Opus 5.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-10-19.
Other skills, from other repositories
gsd-complete-milestone
Archive completed milestone and prepare for next version.
release-finalizer
Merges a release PR, associates it with resolved issues, replies to issue reporters, and closes issues. Use after PR review is complete and ready for merge. Closes the release cycle.
release-prep
Orchestrates the full release preparation flow for a plugin — version sync across 7+ files, bilingual release notes creation, and commit message drafting. Use before submitting a PR. Does NOT push or create a PR; that is handled by pr-submitter.
publish-no-version-bump
Commit and push code to GitHub, then publish to OpenWebUI official marketplace without updating version. Use when fixing bugs or optimizing performance that doesn't warrant a version bump.
update
Safe cc10x upgrade through the Claude Code plugin CLI. Lists every installed scope, refreshes the marketplace, updates each scope, and optionally carries local patches over to the new install. Use this skill when: updating cc10x, upgrading, pulling latest cc10x, syncing plugin, refreshing cache, or checking for new…
03-release-tag
Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.