mastra: Command for Claude Code

.claude/commands/critique-pr.md

critique-pr is a command for Claude Code from mastra-ai/mastra. It costs 0 tokens per session (13 once invoked), scanned A, original, no licence file.

A command for reviewing and giving feedback on a pull request, which is a proposed set of code changes submitted for review.

In plain words
What is it for?
It is intended for critiquing GitHub pull requests.
Why use it?
It may organize pull-request critique, but the description does not explain the checks or feedback it provides.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is mastra-ai/mastra's own configuration. It tells Claude Code how to work on mastra 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 mastra configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mastra-ai/mastra. 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/mastra-ai/mastra/main/.claude/commands/critique-pr.md
Clone the repo
git clone --depth 1 https://github.com/mastra-ai/mastra

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 critique-pr

README.md
[![agentmods](https://agentmods.dev/badge/commands/mastra-ai/mastra/critique-pr/github.svg)](https://agentmods.dev/commands/mastra-ai/mastra/critique-pr)
Your own site
<a href="https://agentmods.dev/commands/mastra-ai/mastra/critique-pr"><img src="https://agentmods.dev/badge/commands/mastra-ai/mastra/critique-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.

agentmods 80×15 button for critique-pr

Your own site · 80×15
<a href="https://agentmods.dev/commands/mastra-ai/mastra/critique-pr"><img src="https://agentmods.dev/badge/commands/mastra-ai/mastra/critique-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 13 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 unknown 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.00000 $0.00013
Opus 5 $0.00000 $0.00006
Sonnet 5 $0.00000 $0.00003
Haiku 4.5 $0.00000 $0.00001

Measured 11d ago against content hash 44f97dce8a50, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

critique-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 11d 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/critique-pr.md · 1 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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. 11d ago First seen · 1 lines · 0 tokens per session scan A 44f97dce8a50

Subscribe to this mod's changes

critique-pr is a command published in the GitHub repository mastra-ai/mastra (27,896 stars, last pushed today), with no licence file. It costs nothing until one of its globs matches a file; then it loads 13 tokens. 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.

Related

Other commands, from other repositories

review

Review code changes against project conventions.

vstorm-co/full-stack-ai-agent-template · 6 tokens

fix-issue

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…

yonatangross/orchestkit · 82 tokens

review-pr

PR review using parallel specialized agents for code quality, security, testing, architecture, and performance analysis. Synthesizes findings into a review report with conventional comments (praise/issue/suggestion/nitpick) and approve or request-changes verdict. Use when reviewing pull requests, conducting security…

yonatangross/orchestkit · 69 tokens

design-ship

One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…

yonatangross/orchestkit · 84 tokens

hatch3r-pr-resolve

Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.

hatch3r/hatch3r · 25 tokens

pr

Analyze changes, detect scope issues, and create a well-structured PR.

FlorianBruniaux/claude-code-plugins · 16 tokens