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/entra-app)<a href="https://agentmods.dev/commands/anthropics/financial-services/entra-app"><img src="https://agentmods.dev/badge/commands/anthropics/financial-services/entra-app.svg" alt="Measured on agentmods" 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.00000 | $0.01718 |
| Opus 5 | $0.00000 | $0.00859 |
| Sonnet 5 | $0.00000 | $0.00344 |
| Haiku 4.5 | $0.00000 | $0.00172 |
Grade A, and why
entra-app 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 8d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Register your own Entra app
Several manifest configurations require an Entra (Azure AD) app registration in
your tenant rather than Anthropic's default multi-tenant app — because the
token's aud must match a resource you control, or because your tenant is in a
sovereign cloud where Anthropic's app doesn't exist. This page is the single
set of registration steps; the per-feature docs link here and tell you which
row of the permissions table applies.
You need this when setting any of:
| Manifest key | Why your own app |
|---|---|
graph_client_id (Outlook) |
Graph permissions are consented against your app, not Anthropic's |
entra_scope |
Access token must be audienced to your API resource |
gateway_auth_source=entra |
Your gateway — or a Foundry resource — validates a token audienced to that resource |
graph_cloud ≠ global |
Anthropic's app exists only in the commercial cloud |
Register the app
In Entra admin center → App registrations → New registration. Single-tenant. The simplest topology is one app acting as both client (the add-in signs in as it) and resource (your backend validates tokens audienced to it); split into two if your policy requires.
1. Redirect URIs
Authentication → Add a platform → Single-page application → add both:
| URI | Used by |
|---|---|
brk-multihub://pivot.claude.ai |
NAA broker — desktop Office and Outlook web. Missing this → AADSTS50011 at sign-in. |
https://pivot.claude.ai/msal-redirect.html |
SPA fallback — Excel/Word/PowerPoint on Office for the web, which don't inject the NAA bridge. |
Both go under the SPA platform (not Web, not Mobile/desktop).
2. Permissions / API setup
What you configure here depends on what the token is for:
| Use case | Configure |
|---|---|
| Outlook (Graph) | API permissions → Microsoft Graph → Delegated → Mail.ReadWrite, Calendars.Read, People.Read, User.Read, offline_access. |
Gateway / bootstrap auth (entra_scope, gateway_auth_source=entra) |
Expose an API → set Application ID URI api://<app-guid> → Add a scope (e.g. access_as_user, admin-consent enabled). Then API permissions → My APIs → add that scope as a delegated permission (the app to itself, in single-app topology). |
Foundry direct, keyless (gateway_auth_source=entra + azure_resource_name) |
API permissions → Azure Cognitive Services → Delegated → user_impersonation. No Expose an API step — the token is audienced to Azure's https://cognitiveservices.azure.com, not your own app, so set entra_scope=https://cognitiveservices.azure.com/.default. Also grant each user the Cognitive Services User role on the Foundry resource (Azure Portal → resource → Access control (IAM)). |
Bedrock WIF (aws_role_arn) |
No API permissions needed — the ID token alone is the web identity. |
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.
- 8d ago First seen · 122 lines · 0 tokens per session scan A 38b3db05b54b
entra-app is a command published in the GitHub repository anthropics/financial-services (34,727 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,718 tokens. 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.