Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rshade/finfocusnpx agentmods add skills/rshade/finfocus/finfocus-plugin-upgradeWrote 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/rshade/finfocus/finfocus-plugin-upgrade)<a href="https://agentmods.dev/skills/rshade/finfocus/finfocus-plugin-upgrade"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/finfocus-plugin-upgrade/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/rshade/finfocus/finfocus-plugin-upgrade"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/finfocus-plugin-upgrade.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.00102 | $0.01653 |
| Opus 5.5 | $0.00041 | $0.00661 |
| Sonnet 5.5 | $0.00020 | $0.00331 |
| Haiku 4.5 | $0.00010 | $0.00165 |
Grade A, and why
finfocus-plugin-upgrade 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinFocus Plugin Upgrade
Move a plugin project to a newer finfocus-spec version. finfocus plugin upgrade makes the edits that need no judgment. This skill covers the rest,
using one migration guide per hop in references/.
A hop ends at a release that needs plugin-author action. Hops are not minor versions: v0.5.7, a patch release, changed a handler signature.
Rules
- Show the plan and get approval before editing anything.
- Work on a new branch from a clean tree. Never stash or discard the user's changes yourself; ask them to commit or stash.
- Change only what a guide or a compile error requires. Do not change
pricing math, adopt optional features, reformat files, or edit
vendor/. - Never delete or skip a failing test to get green. Fix the cause or stop and report it.
- Do not commit unless the user asks.
1. Plan
Run from the plugin's repository root:
finfocus plugin upgrade --dry-run --output json
If plugin upgrade is an unknown command, finfocus is too old: ask the user
to update it. The command never uses the network. The default target is the
finfocus-spec version that this finfocus build uses.
Read the JSON:
| Field | Meaning |
|---|---|
plan.current, plan.target |
Version in go.mod and the version to move to |
plan.up_to_date |
true: stop, there is nothing to do |
plan.required_go |
go directive will be raised to this |
plan.hops[] |
Ordered hops: to, summary, automatic, manual, guide |
plan.warnings[] |
Stale SpecVersion constants, replace directives |
Present the current and target versions, each hop's manual steps, and the
warnings. Ask whether to proceed, and whether to stop at an earlier hop
(--to).
Errors stop the skill:
| Error | Action |
|---|---|
not a FinFocus plugin |
Wrong directory, or go.mod lacks the spec module |
plugin is too old to upgrade |
Below v0.5.0. Suggest finfocus plugin init and porting the pricing code |
plugin is newer than this finfocus build |
Update finfocus first |
What ships with it
11 files 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.
- finfocus-plugin-upgrade.skill 11 KB
- references/to-v0.5.7.md 1.1 KB
- references/to-v0.6.0.md 1.3 KB
- references/to-v0.6.1.md 822 B
- references/to-v0.6.2.md 1.5 KB
- references/to-v0.7.0.md 672 B
- references/to-v0.7.1.md 1.4 KB
- references/to-v0.7.2.md 1.4 KB
- references/to-v0.7.3.md 1.0 KB
- references/to-v0.7.4.md 1.5 KB
- references/to-v0.7.5.md 1.4 KB
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 Changed · +1 lines 0af79ecb917a
- 4d ago Changed · +2 lines 0534500e856a
- 6d ago Changed · +1 lines 31e329a446bc
- 7d ago First seen · 145 lines · 102 tokens per session scan A 37edf278f024
finfocus-plugin-upgrade is a skill published in the GitHub repository rshade/finfocus (10 stars, last pushed today), licensed Apache-2.0. It adds 102 tokens to every session and 1,653 once invoked, about $0.0004 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-10-03.
Other skills, from other repositories
go-linters
Add and validate custom Go analysis linters in gh-aw.
printing-press-polish
Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use…
stack-trace-go-probe
Internal helper for meta-stack-trace-investigator. Use when a Go panic or stack trace needs Go-specific nil/error checks, go test reproducer guidance, and patch targets.
golang-troubleshooting
Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production…
golang-error-handling
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log…
go-concurrency-patterns
Master Go concurrency with goroutines, channels, sync primitives, and context. Use when building concurrent Go applications, implementing worker pools, or debugging race conditions.