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 finfocus-routinggit 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/finfocus-routing)<a href="https://agentmods.dev/skills/rshade/finfocus/finfocus-routing"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/finfocus-routing/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-routing"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/finfocus-routing.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.00101 | $0.01046 |
| Opus 5.5 | $0.00040 | $0.00418 |
| Sonnet 5.5 | $0.00020 | $0.00209 |
| Haiku 4.5 | $0.00010 | $0.00105 |
Grade A, and why
finfocus-routing 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 1mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinFocus Plugin Routing
Route cost queries to the right plugin based on provider, region, patterns, and priority.
No Config = No Routing
Without a routing: section in config.yaml, the engine queries all plugins
for every resource. Add routing config only when you need control.
Config Format
# ~/.finfocus/config.yaml (or $PROJECT/.finfocus/config.yaml)
routing:
plugins:
- name: aws-public # Must match installed plugin name
priority: 10 # Higher = preferred (default: 0)
features: # Limit capabilities (default: all)
- ProjectedCosts
patterns: # Declarative type matching (optional)
- type: glob
pattern: "aws:ec2:*"
fallback: true # Try next on failure (default: true)
Priority and Fallback
- Higher number = higher priority (sorted descending, stable sort)
- Equal priority (all 0) = plugins queried in parallel
- $0.00 is a VALID result — does NOT trigger fallback
- Only nil/empty results or errors trigger fallback to next plugin
InvalidArgumentdoes NOT trigger fallback (plugin explicitly rejected)
Features
| Feature | gRPC Method | Capability |
|---|---|---|
ProjectedCosts |
GetProjectedCost |
PLUGIN_CAPABILITY_PROJECTED_COSTS |
ActualCosts |
GetActualCost |
PLUGIN_CAPABILITY_ACTUAL_COSTS |
Recommendations |
GetRecommendations |
PLUGIN_CAPABILITY_RECOMMENDATIONS |
Carbon |
GetCarbonFootprint |
PLUGIN_CAPABILITY_CARBON |
DryRun |
PerformDryRun |
PLUGIN_CAPABILITY_DRY_RUN |
Budgets |
GetBudgetStatus + 3 others |
PLUGIN_CAPABILITY_BUDGETS |
BatchCost |
BatchCost |
PLUGIN_CAPABILITY_BATCH_COST |
Empty features list = all features enabled. Feature names are case-sensitive.
Pattern Matching
Two types for declarative resource type matching:
What ships with it
2 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.
- 1mo ago First seen · 121 lines · 101 tokens per session scan A a61ffb65c11d
finfocus-routing is a skill published in the GitHub repository rshade/finfocus (10 stars, last pushed today), licensed Apache-2.0. It adds 101 tokens to every session and 1,046 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-08-31.
Other skills, from other repositories
tdd
Test-Driven Development workflow for ALL Prowler components (UI, SDK, API). Trigger: ALWAYS when implementing features, fixing bugs, or refactoring - regardless of component. This is a MANDATORY workflow, not optional.
ak-test
Set up testing and debug common issues in Agent Kernel projects. This skill guides you through configuring the built-in test framework, writing agent tests, choosing test modes (score, llm, fallback), and troubleshooting common errors.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.