claude-tap is a local proxy and trace viewer for AI coding agents, recording and displaying their API requests, prompts, tool calls, responses, context, and token usage. It helps developers inspect and compare agent runs from tools such as Claude Code, Codex CLI, Gemini CLI, Cursor CLI, and others, while the catalogue skills and instruction support work with the project.
Borrowing it
Nothing to install: this file belongs to liaohch3/claude-tap. 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/liaohch3/claude-tap/main/.agents/skills/push-release/SKILL.mdgit clone --depth 1 https://github.com/liaohch3/claude-tapWrote 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/liaohch3/claude-tap/push-release)<a href="https://agentmods.dev/skills/liaohch3/claude-tap/push-release"><img src="https://agentmods.dev/badge/skills/liaohch3/claude-tap/push-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/liaohch3/claude-tap/push-release"><img src="https://agentmods.dev/badge/skills/liaohch3/claude-tap/push-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.00016 | $0.00535 |
| Opus 5.5 | $0.00006 | $0.00214 |
| Sonnet 5.5 | $0.00003 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
push-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 1mo 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
Push & Release
Push code to GitHub. If the pending commits contain feature changes, bump the version number so CI auto-publishes to PyPI.
Workflow
-
Check working tree: Ensure no uncommitted changes (prompt user to commit first if dirty).
-
Determine whether a version bump is needed:
- Read current version from
pyproject.toml - Run
git log origin/main..HEAD --onelineto inspect pending commits - If commits include feature changes (feat/fix/refactor, not purely docs/chore/test), a bump is needed
- If only docs, tests, or CI changes, skip the bump
- Read current version from
-
If bump is needed:
- Choose bump level based on change type:
- patch (0.1.4 → 0.1.5): bug fixes, minor improvements
- minor (0.1.4 → 0.2.0): new features
- major (0.1.4 → 1.0.0): breaking changes
- Update the
versionfield inpyproject.toml - Update
__version__inclaude_tap/__init__.py git commit --amendto fold the version bump into the last commit (avoids extra commits)
- Choose bump level based on change type:
-
Push:
git push origin main -
Confirm CI status:
- Inform the user that CI will automatically: lint → test → auto-tag → PyPI publish
- Provide the GitHub Actions link: https://github.com/liaohch3/claude-tap/actions
Important: Version Bump = PyPI Release
The CI pipeline works as follows: push to main → auto-tag (only if version changed) → PyPI publish (triggered by new tag).
A version bump is the ONLY way to trigger a new PyPI release. If you push without bumping the version, CI will skip tagging and nothing gets published. So whenever commits include meaningful code changes (features, fixes, improvements), you MUST bump the version before pushing.
- Version numbers in
pyproject.tomlandclaude_tap/__init__.pymust stay in sync - Only skip the bump for pure docs/test/CI changes that don't affect the published package
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.
- 1mo ago First seen · 47 lines · 16 tokens per session scan A 665e5b223dd2
push-release is a skill published in the GitHub repository liaohch3/claude-tap (3,311 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 535 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
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.
breaking-changes
Detects breaking changes between two git refs and generates a migration guide.
release-notes
Generates release notes from commits since the last tag.
tag-release
Bumps version in package.json (or equivalent), creates a git tag, and pushes.
changelog
Updates CHANGELOG.md with commits since the last entry.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.