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 commands/husniadil/ekstend/releasegit clone --depth 1 https://github.com/husniadil/ekstendWrote 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/husniadil/ekstend/release)<a href="https://agentmods.dev/commands/husniadil/ekstend/release"><img src="https://agentmods.dev/badge/commands/husniadil/ekstend/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 | $0.00000 | $0.00632 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
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 3d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Workflow
Execute the full release workflow for ekstend plugins.
Steps
1. Version Check and Bump
Check if versions need to be bumped across all version files:
pyproject.toml- root project version.claude-plugin/marketplace.json- marketplace versionplugins/*/. claude-plugin/plugin.json- individual plugin versions (only if plugin was modified)
Ask the user:
What type of version bump is needed?
1. Patch (bug fixes) - e.g., 1.7.0 -> 1.7.1
2. Minor (new features) - e.g., 1.7.0 -> 1.8.0
3. Major (breaking changes) - e.g., 1.7.0 -> 2.0.0
4. No bump needed (versions already updated)
If bump is needed, update all relevant version files consistently.
2. Documentation Check
Review and update documentation if needed:
README.md- root readme (plugin list, installation commands)AGENTS.md- current plugins listplugins/*/README.md- individual plugin readmes
Verify:
- All plugins listed in marketplace.json are documented
- Installation commands match available plugins
- No stale references to removed plugins
3. Pre-commit Hooks
Run all pre-commit hooks manually:
uv run --with pre-commit pre-commit run --all-files
This runs:
- ruff (lint and format)
- mypy (type checking, may update uv.lock)
- prettier (JSON, YAML, Markdown formatting)
If any files are modified, stage them for commit.
4. Commit Changes
Stage all changes and create a commit:
git add -A
git status
Ask user to confirm the changes look correct, then commit with a release message:
Release vX.Y.Z
- [Summary of changes]
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <[email protected]>
5. Tag the Commit
Create an annotated tag:
git tag -a vX.Y.Z -m "vX.Y.Z - [Brief description]"
6. Push to Remotes
Push both the commit and the tag:
git push origin main
git push origin vX.Y.Z
7. Create GitHub Release
Create a new release using GitHub CLI:
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.
- 3d ago First seen · 113 lines · 0 tokens per session scan A 9d63e7c63beb
release is a command published in the GitHub repository husniadil/ekstend (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 632 tokens. 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-31.
Other commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
merge-and-status
Merge the current PR, pull main, surface any open contributor PRs and untriaged contributor issues, and show open milestone issues.
release
Prepare a release by updating docs and bumping the version.