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/ashaychangwani/imprint/releasenpx skills add ashaychangwani/imprint --skill releasegit 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.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.00028 | $0.00624 |
| Opus 5 | $0.00014 | $0.00312 |
| Sonnet 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 6d 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.
- 6d ago First seen · 94 lines · 28 tokens per session scan A c66aec4c82dd
release is a skill published in the GitHub repository ashaychangwani/imprint (21 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 624 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
writing-gauntlet-stories
Use when writing or reviewing a Gauntlet story card. Establishes the calibration framing — outcomes, persona binding, observable acceptance criteria — and explicitly rules out wrong-shaped frames (Agile user stories, QA step-scripts, BDD Given/When/Then) so prior knowledge does not contaminate the card.
release
Cut or diagnose a BrowserMesh release - Release Please PR, protected tag, npm Trusted Publishing over OIDC, and MCP Registry publication. Use when preparing a release, reviewing a Release PR, investigating a failed publish, or asked why a version did not reach npm or the registry.
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) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
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, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.