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-analyzer-setupgit 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-analyzer-setup)<a href="https://agentmods.dev/skills/rshade/finfocus/finfocus-analyzer-setup"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/finfocus-analyzer-setup/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-analyzer-setup"><img src="https://agentmods.dev/badge/skills/rshade/finfocus/finfocus-analyzer-setup.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.00113 | $0.00870 |
| Opus 5.5 | $0.00045 | $0.00348 |
| Sonnet 5.5 | $0.00023 | $0.00174 |
| Haiku 4.5 | $0.00011 | $0.00087 |
Grade A, and why
finfocus-analyzer-setup 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FinFocus Analyzer Setup
Inline cost estimation during pulumi preview via the Pulumi Analyzer protocol.
All diagnostics are ADVISORY — never blocks deployments.
Prerequisites
finfocus --version # FinFocus CLI installed
pulumi version # Pulumi CLI installed
finfocus plugin list # At least one cost plugin installed
Quick Setup
finfocus analyzer install # Install + create policy pack
finfocus analyzer check # Verify all 4 checks pass
# Add to PATH (required for Pulumi to discover the binary)
export PATH="$HOME/.finfocus/analyzer:$PATH"
# Run preview with costs
pulumi preview --policy-pack ~/.finfocus/analyzer
For persistent PATH, add the export to ~/.bashrc or ~/.zshrc.
Windows (PowerShell): Add to your PowerShell profile ($PROFILE):
$env:PATH = "$env:USERPROFILE\.finfocus\analyzer;$env:PATH"
Restart PowerShell for changes to take effect.
What analyzer install Does
- Creates
~/.pulumi/plugins/analyzer-finfocus-v{VERSION}/pulumi-analyzer-finfocus(symlink on Unix, copy on Windows) - Creates
~/.finfocus/analyzer/PulumiPolicy.yaml(runtime: finfocus) - Creates
~/.finfocus/analyzer/pulumi-analyzer-policy-finfocus(binary reference)
Use --force to reinstall after upgrading finfocus. Use --target-dir to
override the Pulumi plugin directory.
Verification
finfocus analyzer check # Table output
finfocus analyzer check --output json # JSON for CI
Runs 4 sequential checks (later checks skip if earlier ones fail):
| Check | Verifies |
|---|---|
policy_pack_dir |
~/.finfocus/analyzer/ exists |
pulumi_policy_yaml |
PulumiPolicy.yaml has runtime: finfocus |
binary_in_path |
pulumi-analyzer-policy-finfocus on PATH |
grpc_smoke_test |
analyzer serve starts and responds to RPC |
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 · 107 lines · 113 tokens per session scan A 588522c5f206
finfocus-analyzer-setup is a skill published in the GitHub repository rshade/finfocus (10 stars, last pushed today), licensed Apache-2.0. It adds 113 tokens to every session and 870 once invoked, about $0.0005 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
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…
gh-aw
Create and maintain GitHub Agentic Workflows (gh-aw) for Prowler. Trigger: When creating agentic workflows, modifying gh-aw frontmatter, configuring safe-outputs, setting up MCP servers in workflows, importing Copilot Custom Agents, or debugging gh-aw compilation.
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.
hyperpod-node-debugger
Diagnose and remediate per-node issues on a HyperPod cluster (EKS or Slurm) — a specific node is unhealthy, unresponsive, stuck, or needs replacing. Covers on-node EFA, GPU / accelerator hardware (XID, ECC, NVLink, row-remap, DCGM), Slurm node down/drained, disk and memory pressure, per-node lifecycle-script failures…
hyperpod-cluster-debugger
Diagnose and remediate cluster-wide HyperPod (EKS or Slurm) problems — creation / deployment failures (CloudFormation, EFA health check, lifecycle scripts, capacity), EKS access, node replacement, CloudFormation nested-stack errors, post-maintenance rollback state, dangling nodes, autoscaler conflicts. Includes…