Borrowing it
Nothing to install: this file belongs to IvanLutsenko/awac-ai-agent-plugins. 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/IvanLutsenko/awac-ai-agent-plugins/main/.claude/commands/publish-plugin.mdgit clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-pluginsWrote 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/commands/ivanlutsenko/awac-ai-agent-plugins/publish-plugin)<a href="https://agentmods.dev/commands/ivanlutsenko/awac-ai-agent-plugins/publish-plugin"><img src="https://agentmods.dev/badge/commands/ivanlutsenko/awac-ai-agent-plugins/publish-plugin/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/commands/ivanlutsenko/awac-ai-agent-plugins/publish-plugin"><img src="https://agentmods.dev/badge/commands/ivanlutsenko/awac-ai-agent-plugins/publish-plugin.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.00596 |
| Opus 5.5 | $0.00006 | $0.00238 |
| Sonnet 5.5 | $0.00003 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
publish-plugin 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
Publish Plugin
Publish plugin after changes: $ARGUMENTS
Step 1: Parse arguments
Extract from $ARGUMENTS:
plugin_name(required) — directory name underplugins/bump_type(optional, default:patch) —patch,minor, ormajor
If no arguments provided, detect which plugin was changed:
Bash: cd "$(git rev-parse --show-toplevel)" && git diff --name-only HEAD | grep '^plugins/' | head -1 | cut -d/ -f2
If multiple plugins changed, ask user which one to publish.
Step 2: Run version bump script
Bash: cd "$(git rev-parse --show-toplevel)" && python3 scripts/publish-plugin.py {plugin_name} {bump_type}
Parse the YAML output — it shows old/new version and which files were updated.
Step 3: Generate changelog
Look at what changed since last version:
Bash: cd "$(git rev-parse --show-toplevel)" && git diff HEAD -- plugins/{plugin_name}/
Based on the diff, write a changelog entry in plugins/{plugin_name}/README.md:
- Find the
## Changelogor## Version Historysection - Add a new
### {new_version}entry BEFORE the previous version - Use concise bullet points describing what changed
- Prefix breaking changes with
**Breaking:**
Step 4: Update root README "What's New"
In the root README.md, find the plugin's section and update **What's New in X.Y.Z:** with a 1-line summary.
Step 5: Verify
Check all files are consistent:
Bash: cd "$(git rev-parse --show-toplevel)" && grep -rn "{new_version}" plugins/{plugin_name}/.claude-plugin/plugin.json plugins/{plugin_name}/.codex-plugin/plugin.json plugins/{plugin_name}/README.md README.md CLAUDE.md .claude-plugin/marketplace.json
Step 6: Commit + push
Bash: cd "$(git rev-parse --show-toplevel)" && git add plugins/{plugin_name}/ README.md CLAUDE.md .claude-plugin/marketplace.json scripts/ && git commit -m "feat({plugin_name}): v{new_version} — {1-line summary}"
Bash: cd "$(git rev-parse --show-toplevel)" && git push
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 · 61 lines · 16 tokens per session scan A d356be464dd3
publish-plugin is a command published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (3 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 596 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-09-05.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.