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/imprint-example-refresh-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/imprint-example-refresh-release)<a href="https://agentmods.dev/skills/ashaychangwani/imprint/imprint-example-refresh-release"><img src="https://agentmods.dev/badge/skills/ashaychangwani/imprint/imprint-example-refresh-release.svg" alt="Measured on agentmods" 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.00062 | $0.00832 |
| Opus 5 | $0.00031 | $0.00416 |
| Sonnet 5 | $0.00012 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
imprint-example-refresh-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 8d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Example Refresh Release
Use this to move verified generated tools into examples/ and publish a patch release.
This complements the repo's release skill; follow that skill for the final version,
tag, push, and npm verification steps.
Before Editing
Rebase before committing, as required by AGENTS.md:
git status --short --branch
git fetch origin main
git rebase origin/main
Inspect the generated site directory and existing example conventions:
find ~/.imprint/<site> -maxdepth 2 -type f | sort
rg --files examples/<site>
find examples -maxdepth 3 \( -name backends.json -o -name integration.test.ts -o -name '*.test.ts' \) -print | sort
Copy Rules
Copy only active tool artifacts. Exclude local state:
node_modules/sessions/- dotfiles such as
.audit-*,.cdp-jar.json,.teach-state.json,.classifications.json,.build-plan.json,.compile-*,.tool-plan.md bun.lock- generated live
integration.test.tsunless the example already commits them - stale partial tool directories that lack complete
index.ts/workflow.json
For generated Google Flights, the active refreshed directories were:
_shared
lookup_flight_locations
get_flight_location_details
get_flight_calendar_prices
search_flights
get_flight_booking_options
validate_flight_itinerary
Use mechanical copy commands for bulk generated artifacts, then use apply_patch for
manual docs or test edits.
Documentation And Tests
Update any root or example README references to old tool counts, old tool names, stale audit percentages, or obsolete producer-token contracts.
If tsconfig.json includes examples/**/*, expect checked-in generated tools to
typecheck. Update repo tests that assert example tool lists or generated parser behavior,
but keep behavioral coverage. For Google Flights, preserve guards that:
- bad/non-batchexecute provider responses throw instead of returning false zeroes;
- one-way encoding works for string and numeric trip-type variants;
- missing return date forces one-way despite round-trip defaults;
- airline filters are rendered as included carriers;
- calendar duplicate dates keep the lowest fare;
- CDP reuse tests use framed batchexecute fixtures and bootstrap HTML matching current captures.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 109 lines · 62 tokens per session scan A ac0a1cf7d8cf
imprint-example-refresh-release is a skill published in the GitHub repository ashaychangwani/imprint (21 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 832 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-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) 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…
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.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.