App: Command for Claude Code

.claude/commands/investigate-deploy-blocker.md

investigate-deploy-blocker is a command for Claude Code from Expensify/App. It costs 14 tokens per session (189 once invoked), scanned A, original, MIT.

A command that investigates a deployment-blocking issue by using a deployment-blocker investigator agent.

In plain words
What is it for?
Use it with an issue URL to analyze the blocker, post findings and a recommended resolution, and update issue labels when appropriate.
Why use it?
It helps determine whether the problem is in the frontend or backend and identifies the pull request most likely to have caused it.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is Expensify/App's own configuration. It tells Claude Code how to work on App itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything App configures →

About the project

Expensify/App is the source code for New Expensify, a financial collaboration application organized around chat. It is used by contributors building and testing the web, iOS, and Android versions of the application. Catalogue add-ons support development workflows such as mobile testing and agent-assisted work on the codebase.

Expensify/App · 5,081 stars · on GitHub · new.expensify.com

Reuse

Borrowing it

Nothing to install: this file belongs to Expensify/App. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Expensify/App/main/.claude/commands/investigate-deploy-blocker.md
Clone the repo
git clone --depth 1 https://github.com/Expensify/App

Made for: Claude Code.

Wrote 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.

agentmods badge for investigate-deploy-blocker

README.md
[![agentmods](https://agentmods.dev/badge/commands/expensify/app/investigate-deploy-blocker/github.svg)](https://agentmods.dev/commands/expensify/app/investigate-deploy-blocker)
Your own site
<a href="https://agentmods.dev/commands/expensify/app/investigate-deploy-blocker"><img src="https://agentmods.dev/badge/commands/expensify/app/investigate-deploy-blocker/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.

agentmods 80×15 button for investigate-deploy-blocker

Your own site · 80×15
<a href="https://agentmods.dev/commands/expensify/app/investigate-deploy-blocker"><img src="https://agentmods.dev/badge/commands/expensify/app/investigate-deploy-blocker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 189 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00189
Opus 5.5 $0.00006 $0.00076
Sonnet 5.5 $0.00003 $0.00038
Haiku 4.5 $0.00001 $0.00019

Measured 2mo ago against content hash f01a19d91d21, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

investigate-deploy-blocker 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 2mo 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.

.claude/commands/investigate-deploy-blocker.md · 13 lines

What it actually says

Investigate the deploy blocker issue at $ISSUE_URL using the deploy-blocker-investigator agent.

The agent will:

  • Analyze the issue to determine if it's a frontend (App) or backend bug
  • Find the most likely causing PR
  • Post a comment with findings and recommendation
  • Update labels if appropriate
Changes

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.

  1. 2mo ago First seen · 13 lines · 14 tokens per session scan A f01a19d91d21

Subscribe to this mod's changes

investigate-deploy-blocker is a command published in the GitHub repository Expensify/App (5,081 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 189 once invoked, about $0.0001 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-30.