Claude for Financial Services is a collection of agents, skills, commands, plugins, and data connectors for investment banking, equity research, private equity, and wealth-management workflows. Financial professionals use it to draft models, memos, research notes, and reconciliations for review by qualified people. The catalogue contains components from these workflows, including agents, skills, plugins, commands, and instructions.
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.
git clone --depth 1 https://github.com/anthropics/financial-servicesWrote 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/commands/anthropics/financial-services/access-policies)<a href="https://agentmods.dev/commands/anthropics/financial-services/access-policies"><img src="https://agentmods.dev/badge/commands/anthropics/financial-services/access-policies/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/commands/anthropics/financial-services/access-policies"><img src="https://agentmods.dev/badge/commands/anthropics/financial-services/access-policies.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.00020 | $0.02400 |
| Opus 5 | $0.00010 | $0.01200 |
| Sonnet 5 | $0.00004 | $0.00480 |
| Haiku 4.5 | $0.00002 | $0.00240 |
Grade A, and why
access-policies 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 10d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure access_policies
access_policies is the add-in's access-control mechanism going forward: a JSON
list of allow/deny statements — IAM-shaped — that decide which
features are available and under what conditions. Where disabled_features is a
single flat list — a feature is on or off for everyone — access_policies gives
you the same off switch plus conditions and effects:
| Want | disabled_features |
access_policies |
|---|---|---|
| Turn a feature off for everyone | ✔ disabled_features='skills.authoring' |
✔ a resource-less deny statement (same effect) |
| Turn a feature off only on certain documents | ✗ | ✔ add a resource (e.g. a sensitivity label) |
| Turn a feature off except for approved documents (allowlist) | ✗ | ✔ "effect": "allow" |
| Attribute the block in UI copy / telemetry | limited | ✔ per-statement description and source |
A statement with no resource is exactly disabled_features — so anything
you'd put there, you can put here. The resource is what adds granularity, and its
type is the extension point: today the resource is a document identified by its
Microsoft Purview sensitivity label (open_file, uploaded_file); further
resource types plug into the same shape without a new config key. New deployments
should start here; disabled_features remains supported for the simple flat case.
Two label-conditioned controls ship today:
- Whether the add-in runs at all on an open document (the
addin.accesskill switch), keyed off the open document's label. - Whether a file may be attached as an upload (
file.upload), keyed off the attached file's own label — Office files and PDFs.
Walk the admin through the four steps below, then hand the finished JSON to manifest as one more key.
1. Get the label GUIDs
Statements match on the label's GUID (mip_label_guid) — stable across
renames and locales. Have the admin pull their taxonomy once with the Purview
compliance PowerShell module (no app registration needed; it uses Microsoft's
first-party sign-in):
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.
- 10d ago First seen · 226 lines · 20 tokens per session scan A 48de8d8f1eb0
access-policies is a command published in the GitHub repository anthropics/financial-services (34,762 stars, last pushed 15d ago), licensed Apache-2.0. It adds 20 tokens to every session and 2,400 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.