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/expensify/app/review-helpdot-prgit 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.00007 | $0.00271 |
| Opus 5 | $0.00003 | $0.00135 |
| Sonnet 5 | $0.00001 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
review-helpdot-pr 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 3d 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.
What it actually says
Perform a comprehensive HelpDot documentation review using two specialized subagents. Both reviewers use the help site governance files in the repo as the source of truth for rules and scoring:
- docs/HELPSITE_NAMING_CONVENTIONS.md — UI referencing, button/tab naming, navigation
- docs/HELP_AUTHORING_GUIDELINES.md — Structure, headings, metadata, AI retrieval, validation
- docs/TEMPLATE.md — YAML frontmatter, heading guidance, FAQ structure
Step 1: Inline Review
Use the helpdot-inline-reviewer agent to:
- Scan all changed documentation files
- Create inline comments for violations of the governance rules above
- Focus on line-specific, actionable feedback
Step 2: Summary Review
Use the helpdot-summary-reviewer agent to:
- Analyze the overall quality of all changes using the governance criteria
- Provide comprehensive assessment with scoring
- Post one top-level PR comment with summary and recommendations
Run both agents and ensure their feedback is posted to the PR.
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.
- 3d ago First seen · 29 lines · 7 tokens per session scan A 92eb9c1f77da
review-helpdot-pr is a command published in the GitHub repository Expensify/App (5,017 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 271 once invoked, about $0.0000 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
git
Git operations with intelligent commit messages and workflow optimization.
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.