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 blockscout/agent-skills --skill bump-skill-versiongit clone --depth 1 https://github.com/blockscout/agent-skillsWrote 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/blockscout/agent-skills/bump-skill-version)<a href="https://agentmods.dev/skills/blockscout/agent-skills/bump-skill-version"><img src="https://agentmods.dev/badge/skills/blockscout/agent-skills/bump-skill-version.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.1 | $0.00079 | $0.01184 |
| Opus 5 | $0.00039 | $0.00592 |
| Sonnet 5 | $0.00016 | $0.00237 |
| Haiku 4.5 | $0.00008 | $0.00118 |
Grade A, and why
bump-skill-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 8d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump Skill Version
Update a skill's version string in every file that references it. This skill works for any skill in the repo: it first applies a shared bump procedure (frontmatter version + marketplace plugin entry), then consults a per-skill reference file for any extra locations specific to that skill.
Usage
Pass <skill-name> <new-version> as $ARGUMENTS (e.g., blockscout-analysis 0.5.0). If either is missing, ask the user before proceeding.
<skill-name> must match a top-level skill directory in the repo root (e.g., blockscout-analysis/, web3-dev/). Verify the directory and its SKILL.md exist before making any edit.
Shared procedure (applies to every skill)
These three edits are required for every skill bump.
1. <skill-name>/SKILL.md — frontmatter metadata
The YAML frontmatter contains a single-line JSON metadata field with a "version" key:
metadata: {"author":"blockscout.com","version":"<OLD>","github":...}
Replace "version":"<OLD>" with "version":"<NEW>". Use exact strings — do not use regex replacements.
2. .claude-plugin/marketplace.json — plugin entry version
The marketplace manifest has a plugins array; each entry has its own "name" and "version" fields. The bare string "version": "<OLD>" may appear in more than one plugin entry when versions happen to coincide, so the old_string passed to Edit must include the "name" line of the target plugin to disambiguate. Match a block like this:
"name": "<skill-name>",
"description": "...",
"source": "./<skill-name>/",
"strict": false,
"version": "<OLD>",
Replace only the "version": "<OLD>" line within that block with "version": "<NEW>". Leave the top-level marketplace metadata.version untouched — it tracks the marketplace as a whole, not the individual skill.
3. .agents/plugins/<skill-name>/.codex-plugin/plugin.json — codex plugin descriptor
Each skill that ships as a Codex plugin has its own descriptor at .agents/plugins/<skill-name>/.codex-plugin/plugin.json. The descriptor is dedicated to one skill, so the version field is unambiguous — but include the "name" line in the old_string anyway as a sanity check that the right file is being edited:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 78 lines · 79 tokens per session scan A 2d248b80e303
bump-skill-version is a skill published in the GitHub repository blockscout/agent-skills (35 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 1,184 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…