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/erraggy/oastools/prepare-releasenpx skills add erraggy/oastools --skill prepare-releasegit clone --depth 1 https://github.com/erraggy/oastoolsWrote 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/erraggy/oastools/prepare-release)<a href="https://agentmods.dev/skills/erraggy/oastools/prepare-release"><img src="https://agentmods.dev/badge/skills/erraggy/oastools/prepare-release.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.00050 | $0.02249 |
| Opus 5 | $0.00025 | $0.01125 |
| Sonnet 5 | $0.00010 | $0.00450 |
| Haiku 4.5 | $0.00005 | $0.00225 |
Grade A, and why
prepare-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 3d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prepare-release
Prepare a new release by running comprehensive pre-release checks and updates.
Usage:
/prepare-release <version>- Use specified version (e.g.,/prepare-release v1.46.0)/prepare-release- Infer version from conventional commits
Version Inference
If no version is provided, analyze commits since the last tag:
Step 1: Get Commits Since Last Release
LAST_TAG=$(git describe --tags --abbrev=0)
echo "Last release: $LAST_TAG"
git log "$LAST_TAG"..HEAD --oneline
Step 2: Determine Version Bump
Parse conventional commit prefixes:
- Any
BREAKING CHANGE:footer or type with exclamation suffix (e.g.,feat!:,fix!:) → MAJOR bump - Any
feat:orfeat(scope):→ MINOR bump - Only
fix:,chore:,docs:,refactor:,test:,perf:→ PATCH bump
Step 3: Propose or Prompt
If clear signal: Propose the version with explanation:
Analyzing commits since v1.45.2...
Found 4 commits:
- feat(parser): add streaming support
- fix(validator): handle empty schemas
- chore: update dependencies
- docs: improve examples
Recommendation: **v1.46.0** (minor bump due to new feature)
Proceed with v1.46.0? [Yes / Different version]
If ambiguous: Prompt user to choose:
Analyzing commits since v1.45.2...
Found 3 commits with unclear versioning signal:
- refactor(core): reorganize internal structure
- perf: optimize memory usage
- chore: update dependencies
What version bump is appropriate?
- v1.45.3 (patch) - Bug fixes and minor improvements
- v1.46.0 (minor) - Notable improvements worth a minor bump
- Other - Specify a different version
Process
You are the DevOps Engineer coordinating a release. Execute the following phases:
Phase 1: Launch Background Agents
Launch these agents in background mode (run_in_background: true) to run concurrently:
- DevOps Engineer - Pre-release validation:
- Check commits since last release tag
- Run
make bench-quickfor quick local regression check (~2 min) - Create feature branch
chore/<version>-release-prep
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.
- 3d ago First seen · 273 lines · 50 tokens per session scan A 26718ae58c3f
prepare-release is a skill published in the GitHub repository erraggy/oastools (5 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 2,249 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-31.
Other skills, from other repositories
openapi-glossary
Use consistent OpenAPI terminology and definitions when writing documentation, educational material, and tooling guidance.
scalar-docs
Skill for writing and updating scalar.config.json — Scalar Docs configuration reference for users and LLMs.
scalar-design-system
Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library. Use when designing or implementing Scalar UI, especially with Paper (code-to-design / design-to-code), so output matches real Scalar tokens, colors, typography, spacing, and components instead of…
cloud-agents-starter
Minimal starter runbook for cloud agents to install dependencies, run packages, execute tests, and troubleshoot the Scalar monorepo quickly.
mock-server
Build, customize, and troubleshoot OpenAPI mock servers with @scalar/mock-server, including x-handler, x-seed, authentication, and Docker.
tests
Write clear, maintainable Vitest and Playwright tests with precise assertions, consistent structure, and strong behavioral coverage.