Borrowing it
Nothing to install: this file belongs to K-dash/typemux-cc. 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/K-dash/typemux-cc/main/.claude/skills/publish/SKILL.mdgit clone --depth 1 https://github.com/K-dash/typemux-ccWrote 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/k-dash/typemux-cc/publish)<a href="https://agentmods.dev/skills/k-dash/typemux-cc/publish"><img src="https://agentmods.dev/badge/skills/k-dash/typemux-cc/publish.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.00038 | $0.00882 |
| Opus 5 | $0.00019 | $0.00441 |
| Sonnet 5 | $0.00008 | $0.00176 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
publish 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish
CI/CD Pipeline
release.yml builds release binaries for 3 targets and creates the GitHub Release with binary assets:
aarch64-apple-darwin(macOS ARM64)x86_64-unknown-linux-gnu(Linux x86_64)aarch64-unknown-linux-gnu(Linux ARM64)
Flow: version-bump PR merges to main → release.yml's preflight job tags the merge
commit itself → same run builds the 3 binaries and creates the GitHub Release. There is no
separate manual tag step: tagging is part of the automated pipeline, not a step this skill
performs.
The v* tag-push trigger still exists as a manual/emergency escape hatch (see the last
section below) but is not part of the normal flow.
Version Locations
Version must be updated in 3 files (all must match):
Cargo.toml—versionfield.claude-plugin/plugin.json—versionfield.claude-plugin/marketplace.json—versionfield insideplugins[0]
Version Bump Workflow
Step 1: Pre-flight checks
git branch --show-current # Must not be main when files are changed
git status # Must be clean
git fetch --tags --quiet
Show the latest tag and current Cargo.toml version. If currently on main, create a
release preparation branch before changing files.
Step 2: Ask for the new version
Use AskUserQuestion. Show the current version and suggest semver options (patch, minor, major).
Step 3: Update version
- Use the Edit tool to update the
versionfield in all 3 files:Cargo.toml.claude-plugin/plugin.json.claude-plugin/marketplace.json
- Run
cargo check --quietto regenerateCargo.lock. - Show
git difffor user review.
Step 4: Prepare a pull request
Ask for explicit authorization before each of the following actions. Authorization for one action does not authorize the next one.
git add Cargo.toml Cargo.lock .claude-plugin/plugin.json .claude-plugin/marketplace.json
git commit -m "chore: bump version to <NEW_VERSION>"
git push -u origin <release-branch>
gh pr create
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 · 96 lines · 38 tokens per session scan A 79e9b293ba7a
publish is a skill published in the GitHub repository K-dash/typemux-cc (16 stars, last pushed 7d ago), licensed MIT. It adds 38 tokens to every session and 882 once invoked, about $0.0002 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
flow-next-land
Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
last-tag
Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.
release-management
Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.