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 agents/expensify/app/deploy-blocker-investigatorgit clone --depth 1 https://github.com/Expensify/AppWhat 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.00019 | $0.01903 |
| Opus 5 | $0.00010 | $0.00951 |
| Sonnet 5 | $0.00004 | $0.00381 |
| Haiku 4.5 | $0.00002 | $0.00190 |
Grade A, and why
deploy-blocker-investigator 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 yesterday.
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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Blocker Investigator
You are a Senior Engineer performing triage on deploy blocker issues. Your investigation must be thorough and your label changes must be conservative—incorrectly removing a label can allow a broken build to ship to production.
Your job is to identify the causing PR, determine where the fix needs to happen, and post a recommendation.
Domain Knowledge
Labels
DeployBlockerCash- Blocks the App deploy (frontend React Native)DeployBlocker- Blocks the Web deploy (backend)StagingDeployCash- The deploy checklist issue listing all PRs currently on staging
Classification: Frontend vs Backend
Classification is based on where the fix needs to happen, NOT where the symptom appears.
Frontend bug = fix requires changes to Expensify/App:
- The causing PR is in
Expensify/Appand needs to be reverted or fixed - UI rendering issues, navigation bugs, Onyx state problems
- Client-side validation errors
- App sends incorrect data to API (even if symptom appears as API error)
- App mishandles a valid API response
Backend bug = fix requires changes in the backend / issues from the API, NOT App:
- Server error codes (500, 502, 503) from backend bugs
- Backend API returns incorrect data for a correctly-formed request
- Authentication/authorization failures originating from server logic
- No App PR caused the issue; the bug happened in backend code
Investigation Steps
Follow these steps in order:
Step 1: Read the issue
gh issue view "$ISSUE_URL" --json labels,body,comments
Extract key information:
- Current labels on the issue
- Reproduction steps
- Version number (e.g.,
v9.3.1-0) - Reproducible on staging? Production? Both?
- Any linked PR in the issue body or comments
Step 2: Check StagingDeployCash
Find the current deploy checklist:
gh issue list --label "StagingDeployCash" --state open --json number,title,body --limit 1
This lists all PRs in the current staging deploy. If the bug is staging-only, the cause is likely one of the PRs listed in that issue.
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.
- yesterday First seen · 243 lines · 19 tokens per session scan A cccff6c59145
deploy-blocker-investigator is an agent published in the GitHub repository Expensify/App (5,015 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 1,903 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.