Borrowing it
Nothing to install: this file belongs to ashaychangwani/imprint. 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/ashaychangwani/imprint/main/.agents/skills/release/SKILL.mdgit clone --depth 1 https://github.com/ashaychangwani/imprintWrote 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/ashaychangwani/imprint/release)<a href="https://agentmods.dev/skills/ashaychangwani/imprint/release"><img src="https://agentmods.dev/badge/skills/ashaychangwani/imprint/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/ashaychangwani/imprint/release"><img src="https://agentmods.dev/badge/skills/ashaychangwani/imprint/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00028 | $0.00624 |
| Opus 5.5 | $0.00011 | $0.00250 |
| Sonnet 5.5 | $0.00006 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
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 2mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill
Cut a new release for Imprint. Follow these steps in order.
Step 1 — Determine bump type
Run git log $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)..HEAD --oneline to see commits since the last tag.
Decide the bump type:
- major — breaking changes (
feat!:orBREAKING CHANGEin body) - minor — new features (
feat:) - patch — everything else (
fix:,refactor:,perf:,docs:,chore:, etc.)
If unsure, ask the user.
Step 2 — Read current version
Read package.json and extract the current version field.
Step 3 — Compute new version
Apply semver bump to the current version. For example: 0.1.0 + minor = 0.2.0.
Step 4 — Update package.json
Edit package.json to set the new version string. Do not change anything else.
Step 5 — Preview changelog
Run bunx git-cliff --config cliff.toml --unreleased --strip header and show the output to the user. Ask if it looks correct.
Step 6 — Commit
Stage and commit:
git add package.json
git commit -m "chore(release): v<VERSION>"
Use the exact version string. No Co-Authored-By trailer for release commits.
Step 7 — Tag
git tag v<VERSION>
Step 8 — Push
Ask the user for confirmation, then:
git push && git push --tags
This triggers the release.yml workflow, which creates the GitHub Release, publishes the npm package, and uploads binaries.
Step 9 — Watch publish
Watch the release workflow:
gh run list --workflow release.yml --limit 1
gh run watch <RUN_ID> --exit-status
Then verify npm:
npm view imprint-mcp version
If GitHub Actions cannot publish and local npm auth is available, publish manually from the tagged commit:
npm whoami
npm publish --access public
Step 10 — Confirm
Tell the user: "Release v<VERSION> tagged and pushed. GitHub Actions created the release at https://github.com/ashaychangwani/imprint/releases, and npm shows imprint-mcp@<VERSION>."
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.
- 2mo ago First seen · 94 lines · 28 tokens per session scan A c66aec4c82dd
release is a skill published in the GitHub repository ashaychangwani/imprint (24 stars, last pushed 15d ago), licensed MIT. It adds 28 tokens to every session and 624 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
bxc-build
Build the bxc Rust bridge, Bun standalone binaries, and native MCP server when a bxc project needs a release or cross-platform artifact.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.