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 rshade/finfocus --skill plugin-managegit clone --depth 1 https://github.com/rshade/finfocusWrote 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/plugin-manage)<a href="https://agentmods.dev/skills/rshade/finfocus/plugin-manage"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/plugin-manage/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/plugin-manage"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/plugin-manage.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.00167 | $0.01950 |
| Opus 5.5 | $0.00067 | $0.00780 |
| Sonnet 5.5 | $0.00033 | $0.00390 |
| Haiku 4.5 | $0.00017 | $0.00195 |
Grade A, and why
plugin-manage 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 yesterday.
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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinFocus Plugin Management
Drive finfocus plugin * for the user. Read state first, preview with
--dry-run before changing it, and verify after.
Workflow
- Inspect state:
finfocus plugin list --output json(installed) andfinfocus plugin list --available(embedded registry, no plugin launch). - Change state: install, update, or remove (below). Preview with the global
--dry-runfirst. It prints what would happen and changes nothing. - Verify:
finfocus plugin validate, thenfinfocus plugin list --verbose. - Check routing if a plugin installs but is never queried:
finfocus config routes test <resource-type> [region].
Never pass --skip-checksum or --force on a first attempt. Use them only after
the diagnosis in references/troubleshooting.md
points there, and tell the user why.
Discover
finfocus plugin list # table
finfocus plugin list --verbose # capabilities, spec version, providers
finfocus plugin list --output json # array of name, version, path, specVersion,
# runtimeVersion, supportedProviders,
# capabilities, notes
finfocus plugin list --available # registry catalog
list launches each installed plugin (5 s timeout each, concurrently) to read
runtime metadata. A plugin that cannot start stays in the output with
notes: "Failed: <error>", so read notes rather than assuming it is absent.
Official registry plugins: aws-public, azure-public, opencost, flexera,
vantage, kubernetes, scorer, carbon, and deprecated jev. Details and provider mapping:
references/registry-and-layout.md.
Install
finfocus plugin install aws-public # registry, latest
finfocus plugin install [email protected] # pinned
finfocus plugin install github.com/owner/finfocus-plugin-x # not in the registry
finfocus plugin install github.com/owner/[email protected]
finfocus plugin install aws-public --metadata="region=us-west-2"
What ships with it
3 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.
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.
- yesterday Changed d05359d16d24
- 2d ago First seen · 187 lines · 167 tokens per session scan A 082afc846340
plugin-manage is a skill published in the GitHub repository rshade/finfocus (10 stars, last pushed today), licensed Apache-2.0. It adds 167 tokens to every session and 1,950 once invoked, about $0.0007 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-19.
Other skills, from other repositories
aws-cost-ops
AWS Cost Explorer — spending analysis, service breakdowns, forecasts, cost anomalies. Use when analyzing AWS spending, investigating cost spikes, reviewing network cost drivers like NAT Gateway, or forecasting next month's bill.
dashboards
Use when creating or extending Costory dashboards, generating interesting FinOps overviews (suggestgroupby + suggestusagemetrics + text widgets), adding or replacing widgets, copying widgets between dashboards, editing dashboardContext (global filter / period / groupBy) via updatedashboard, or applying shared-context…
reports
Use when creating, previewing, updating, scheduling, or exploring Costory reports. Route by intent: scheduled Slack/Teams/email sharing (Schedule — ask before build) vs explain last-month cost with preview-first DIGEST (Explain — chat preview required; not query+compare). Workflows are named, never lettered. DIGEST AI…
query
Use when exploring Costory cost, usage, metric, formula, budget, or external-metric data with the query tool — scope vs split (filterCel / groupBy), explorer PoP comparison, CEL discovery, unit economics, budgets. Not for one-shot "what changed last month" change trees — those use recipes explain-period-change /…
bigquery
Use when the user asks about BigQuery costs, SKUs, on-demand Analysis vs capacity slots/editions, leftover on-demand, physical vs logical storage, time travel or fail-safe, streaming ingest, load/import jobs consuming a reservation, dbt or job labels, slot cost reallocation, dataset/table storage allocation, or…
cost-change-investigation
Use when investigating a cost change to explain what changed, when, and the best-supported drivers with contribution, timing, usage, metric, event, alert, and terminology evidence. Call getskill with skillId "cost-change-investigation" before starting the investigation.