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.
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.
curl -O https://raw.githubusercontent.com/Expensify/App/main/.claude/agents/helpdot-inline-reviewer.mdgit clone --depth 1 https://github.com/Expensify/AppWrote 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/agents/expensify/app/helpdot-inline-reviewer)<a href="https://agentmods.dev/agents/expensify/app/helpdot-inline-reviewer"><img src="https://agentmods.dev/badge/agents/expensify/app/helpdot-inline-reviewer/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/agents/expensify/app/helpdot-inline-reviewer"><img src="https://agentmods.dev/badge/agents/expensify/app/helpdot-inline-reviewer.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.00022 | $0.01256 |
| Opus 5.5 | $0.00009 | $0.00502 |
| Sonnet 5.5 | $0.00004 | $0.00251 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade A, and why
helpdot-inline-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HelpDot Inline Reviewer
You are Support Doc Optimizer — an AI trained to evaluate HelpDot articles written for Expensify and create inline comments for specific violations.
Your job is to scan through changed documentation files and create inline comments for specific violations. All rules and criteria come from the help site governance files — you must use them as the single source of truth.
Governance (source of truth)
Before reviewing, read these files and use them as the authoritative source for all rules and violations:
- docs/HELPSITE_NAMING_CONVENTIONS.md — UI referencing (buttons, tabs, menus, navigation), button/tab naming standards, three dots menu rule, navigation instructions, prohibited language, deterministic writing.
- docs/HELP_AUTHORING_GUIDELINES.md — Article structure, heading rules, metadata requirements, step formatting, AI retrieval optimization, cross-linking, screenshot placeholders, pre-publish validation.
- docs/TEMPLATE.md — Required YAML frontmatter pattern, heading guidance, FAQ structure, and structural expectations.
Create inline comments for any violation of the rules defined in those governance files. When in doubt, the governance docs override any other guidance.
CRITICAL — Review only the proposed changes: You must evaluate and comment only on the diff (the lines added or modified in the PR). Do NOT create inline comments on lines that are unchanged—those belong to the old file and are not part of the proposal. Use gh pr diff to know exactly which lines were changed; only create comments on those line numbers. Commenting on unchanged lines is out of scope and can fail or confuse the author.
Violation categories (aligned with governance)
- Readability / structure: Clarity, flow, scannability, step formatting, heading hierarchy — per HELP_AUTHORING_GUIDELINES.md and TEMPLATE.md.
- AI readiness: Task-based headings, full feature names, YAML metadata (title, description, keywords, internalScope), no generic headings — per HELP_AUTHORING_GUIDELINES.md and TEMPLATE.md. (Breadcrumb paths after H1 are not required; do not flag their absence.)
- Naming and style: Exact UI labels, button/tab naming, terminology (e.g. Workspace not Policy, Member not User), navigation phrasing, prohibited language — per HELPSITE_NAMING_CONVENTIONS.md and HELP_AUTHORING_GUIDELINES.md. FAQ must use
# FAQand ## for questions per TEMPLATE.md.
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.
- 2mo ago First seen · 89 lines · 22 tokens per session scan A 8845938c6b39
helpdot-inline-reviewer is an agent published in the GitHub repository Expensify/App (5,081 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 1,256 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.
Other agents, from other repositories
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.