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 skills add hyhmrright/logic-lens --skill bump-versiongit clone --depth 1 https://github.com/hyhmrright/logic-lensWrote 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/hyhmrright/logic-lens/bump-version)<a href="https://agentmods.dev/skills/hyhmrright/logic-lens/bump-version"><img src="https://agentmods.dev/badge/skills/hyhmrright/logic-lens/bump-version/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/hyhmrright/logic-lens/bump-version"><img src="https://agentmods.dev/badge/skills/hyhmrright/logic-lens/bump-version.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.00052 | $0.00347 |
| Opus 5 | $0.00026 | $0.00173 |
| Sonnet 5 | $0.00010 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
bump-version 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 9d 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
bump-version
Logic-Lens keeps the version in six places (see CLAUDE.md → Version Sync). Hand-editing them drifts; validate-repo.sh only detects drift. This skill rewrites all six atomically via scripts/bump-version.py.
Steps
- Pick the target version. If the user passed one in
$ARGUMENTS, use it. Otherwise readpackage.json's currentversionand ask whether to bump patch / minor / major. - Run the bump from the repo root:
It rewrites thenpm run bump-version -- <new-version> # e.g. npm run bump-version -- 0.7.0versionfield inpackage.json,.claude-plugin/plugin.json,.claude-plugin/marketplace.json,.codex-plugin/plugin.json,gemini-extension.json, and theREADME.mdbadge — preserving formatting — then runsvalidate-repo.sh. - Confirm the run ends with "All checks passed." If any file is reported as a mismatch, stop and report which one — do not hand-edit around the script.
- CHANGELOG.md is not touched. For a real release, add a
CHANGELOG.mdentry for the new version yourself.
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.
- 9d ago First seen · 21 lines · 52 tokens per session scan A a456af489387
bump-version is a skill published in the GitHub repository hyhmrright/logic-lens (22 stars, last pushed 10d ago), licensed MIT. It adds 52 tokens to every session and 347 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
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
release-docs
Diff-driven documentation sync after a release. Determines what source files changed, delegates changelog to zuvo:docs, updates only docs whose source changed. Flags: --dry-run, explicit range argument.
publish
Use when the user invokes /evo:publish or asks to release a new version, ship a release, or publish a tag. Wraps the go-native self-healing release pipeline (evolve release) — pre-flight checks, auto-changelog, atomic ship, marketplace propagation poll, auto-rollback on failure.
release
Use when the user asks whether a release is ready, or to gate/verify release criteria before publishing. A thin readiness-gate that runs the existing read-only verifiers (evolve release-preflight, evolve release-consistency), adds the CI-green-on-main and no-WIP-commit checks they don't cover, then delegates execution…
verify-release
Use when the user invokes /evo:verify-release or asks to check whether a release has propagated, whether the marketplace is up to date, or whether installed plugins reflect the latest version. Wraps legacy/scripts/release/marketplace-poll.sh for standalone post-publish verification.
ship
Use after audit returns Verdict PASS. Atomic git commit + tag + ledger update. Single-writer; cannot fan-out.