Borrowing it
Nothing to install: this file belongs to CRJFisher/ariadne. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CRJFisher/ariadne/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/CRJFisher/ariadneWrote 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/crjfisher/ariadne/release)<a href="https://agentmods.dev/skills/crjfisher/ariadne/release"><img src="https://agentmods.dev/badge/skills/crjfisher/ariadne/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.1 | $0.00026 | $0.00430 |
| Opus 5 | $0.00013 | $0.00215 |
| Sonnet 5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
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 7d 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
Release Preparation
See docs/RELEASING.md for the full release process.
Checklist
- Verify clean working tree:
git status— no uncommitted changes - Build:
pnpm build - Test:
pnpm test - Typecheck:
pnpm typecheck - Create changesets: Add
.changeset/<name>.mdfiles describing the bumps - Verify:
pnpm changeset status— confirm expected version bumps - Commit: Commit changesets and any release-related changes
- Create PR:
gh pr createtargetingmain
Changeset Template
---
"@ariadnejs/core": minor
"@ariadnejs/types": minor
---
Summary of core + types changes
- Change 1
- Change 2
---
"@ariadnejs/mcp": minor
---
Summary of MCP changes
- Change 1
- Change 2
PR Template
## Summary
- Package version bumps: core vX.Y.0, types vX.Y.0, mcp vX.Y.0
- <bullet summary of major changes>
## Pre-release verification
- [x] `pnpm build` passes
- [x] `pnpm test` passes
- [x] `pnpm typecheck` passes
- [x] `pnpm changeset status` shows expected bumps
## Test plan
- [ ] CI passes on this PR
- [ ] Merge to main creates "Version Packages" PR
- [ ] Version Packages PR shows correct version bumps
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.
- 7d ago First seen · 65 lines · 26 tokens per session scan A 71d08157dccb
release is a skill published in the GitHub repository CRJFisher/ariadne (22 stars, last pushed 3d ago), licensed MIT. It adds 26 tokens to every session and 430 once invoked, about $0.0001 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
sem
Use sem to get entity-level (function/class/method) semantic diffs, impact analysis, blame, and dependency context from any Git repo. Trigger this skill whenever the user asks what changed in a commit or PR, wants to understand the blast radius of a change, needs to know who last modified a function, wants to trace…
sem
Semantic version control CLI. Entity-level diffs for Git (functions, classes, methods instead of lines).
poly-and-release-workflow
Commit step lint/test/harness order.
oxc-docs
Comprehensive reference for the JavaScript Oxidation Compiler (Oxc) — a collection of high-performance JavaScript tools written in Rust. Covers parser design (lexer, AST, parser, errors, semantic analysis), architecture (parser, linter, test infrastructure, AST tools), ECMAScript specification and grammar, performance…
release-notes
Compose human-readable release notes from a commit range and changelog.
ensemble-full-implement-trd
This command implements a complete Technical Requirements Document (TRD) using modern git-town feature branch workflow. It creates a feature branch and delegates to ensemble-orchestrator which routes to tech-lead-orchestrator for structured TDD-based development including planning, implementation, testing, and quality…