Dograh is an open-source, self-hostable platform for building voice AI agents that combine speech recognition, language models, and speech synthesis. Teams use its visual workflow builder and telephony integrations to create and operate voice agents while choosing their own providers and infrastructure.
Borrowing it
Nothing to install: this file belongs to dograh-hq/dograh. 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/dograh-hq/dograh/main/.agents/skills/review-pr/SKILL.mdgit clone --depth 1 https://github.com/dograh-hq/dograhWrote 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/skills/dograh-hq/dograh/review-pr)<a href="https://agentmods.dev/skills/dograh-hq/dograh/review-pr"><img src="https://agentmods.dev/badge/skills/dograh-hq/dograh/review-pr/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/skills/dograh-hq/dograh/review-pr"><img src="https://agentmods.dev/badge/skills/dograh-hq/dograh/review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00109 | $0.02705 |
| Opus 5.5 | $0.00044 | $0.01082 |
| Sonnet 5.5 | $0.00022 | $0.00541 |
| Haiku 4.5 | $0.00011 | $0.00270 |
Grade A, and why
review-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 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing PRs (dograh)
This skill is for reviewing any PR, including PRs written by maintainers. Focus on Dograh-specific regression risks. Skip generic lint, formatting, and type-check comments unless they connect to one of the repo-specific issues below.
The main failure modes in this repo are:
- Missing org scoping on request-reachable reads or writes
- Authless routes or websockets
- Trusting unsigned webhook fields
- SQL written outside
api/db/*_client.py - Per-worker cache state updated without worker sync
- UI calls that bypass the generated SDK
- Migrations that are not safe on existing production data
How to drive the review
- Get the diff:
- GitHub PR:
gh pr diff <N>orgh pr view <N> --json files,additions,deletions - Local branch:
git diff origin/main...HEAD
- GitHub PR:
- Bucket changed files into the sections below.
- Run only the sections relevant to the changed files.
- Report findings as
<file>:<line> -> <problem> -> <correct pattern>.
Freshness rule
Treat this file as review policy and navigation, not as a frozen inventory.
- If the current repo conflicts with this skill, trust the repo and mention the drift.
- Do not rely on static allowlists or exact line numbers from this file.
- Review against the code in the PR and the current local repo, not against old prose.
File to section map
| Path pattern in diff | Sections to run |
|---|---|
api/routes/*.py |
1, 2, 8 |
api/db/*_client.py, api/db/models.py |
2, 3 |
api/services/**/*.py |
2, 3, 4 |
api/tasks/*.py |
2, 3, 5 |
api/alembic/versions/*.py |
6 |
api/mcp_server/**, api/services/workflow/mcp_*.py |
1, 2, 7 |
ui/** |
9 |
api/constants.py, anything os.getenv |
10 |
api/tests/** |
11 |
api/schemas/*.py |
12 |
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 · 282 lines · 109 tokens per session scan A 623fc749a2f9
review-pr is a skill published in the GitHub repository dograh-hq/dograh (5,981 stars, last pushed today), licensed BSD-2-Clause. It adds 109 tokens to every session and 2,705 once invoked, about $0.0004 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 skills, from other repositories
release
Cut and maintain Observal release branches, prepare alpha, beta, RC, stable, and patch releases, backport merged main PRs, inspect release status, verify published artifacts, and recover failed release operations. Use for Observal maintainer release tasks and release-process changes, not for installing or upgrading an…
github
Interact with GitHub (issues, PRs, repos, releases) using the gh CLI. Use when asked to read or write GitHub state — open an issue, fetch PR diff, comment, list runs, etc.
review-prs
Triage open PRs — screen from the diff, delegate the admission judgment to audit-the-list, then merge or close on GitHub. Fire when the maintainer asks to review PRs, process the PR queue, or judge whether a specific PR should be merged.
working-in-turns
Keep each turn bounded, checkpointed, and reviewable.
review-preflight
Review tooling for a PR: review-preflight prints REVIEW.md's criteria and the PR's live gate state before a review; ci-triage maps a PR's failing checks to already-filed issues.
reviewing-personhog-protocol
The full review process for personhog coordination-protocol changes — leases, fencing, handoffs, supervisors, failure budgets, warming, and changelog semantics. Use before pushing or requesting review on any personhog protocol changeset, when asked for an exhaustive or careful review of personhog code, and after any…