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 agentmods add commands/anthropics/financial-services/debuggit clone --depth 1 https://github.com/anthropics/financial-servicesWhat 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 | $0.00016 | $0.03921 |
| Opus 5 | $0.00008 | $0.01961 |
| Sonnet 5 | $0.00003 | $0.00784 |
| Haiku 4.5 | $0.00002 | $0.00392 |
Grade A, and why
debug 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 2d 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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug a Claude Office deployment
You are helping an enterprise admin diagnose why the deployed add-in isn't working right. Start by asking what's wrong, then route.
Triage
Ask the admin to describe the symptom. Route by answer:
| Symptom | Section |
|---|---|
| Updated the manifest but users still see old config | Stale config after update |
| Add-in shows "Connection failed" | Read the error paste |
| Add-in doesn't appear in Excel/PowerPoint at all | Add-in not visible |
| Want to test/iterate a manifest locally before deploying | Sideload a manifest for local debugging |
| Sign-in popup fails or loops | Admin consent |
| Need to see the browser console | Opening browser devtools |
If they have an error paste from the add-in (the Copy error details button on the connect-failed screen), always start there. It carries everything.
Read the error paste
Paste structure:
Claude for Office connection failed (<Provider>)
Build: <sha>
<friendly message>
Request:
<key>: <value actually sent>
...
Manifest params:
<key>: <value the deployed manifest carries>
...
Raw error:
<SDK/HTTP error>
What to check:
Request:vsManifest params:delta. Keys are the same snake_case names in both blocks, so diff directly. If they differ, the user typed override values into the form. If they match, the manifest values went through unchanged.Manifest params:mkey is the version tag (e.g.unified-1.0.0.11). If it's below what you last uploaded, the user is on a stale manifest. Go to Stale config.Raw error:is the ground truth. Common patterns:invalid_client(401, Google) → wronggoogle_client_secretfor thatgoogle_client_id. Verify in GCP Console → Credentials.Load failed (<host>)→ network blocked at the WebView layer. Firewall needs to allow that host.STS AssumeRoleWithWebIdentity failed→ AWS IAM OIDC provider misconfigured or role trust policy wrong.HTTP 401/403(gateway) → bad token or gateway rejected the key.
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.
- 2d ago First seen · 359 lines · 16 tokens per session scan A 68128b967a22
debug is a command published in the GitHub repository anthropics/financial-services (34,594 stars, last pushed 7d ago), licensed Apache-2.0. It adds 16 tokens to every session and 3,921 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.