Payload is an open-source, full-stack framework for Next.js that provides a TypeScript backend and an administration panel for managing application data and content. Developers use it as a headless content management system or as the backend and application framework for their own projects. The catalogue add-ons help agents work with Payload projects and their development workflows.
Borrowing it
Nothing to install: this file belongs to payloadcms/payload. 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/payloadcms/payload/main/.claude/commands/analyze-issue.mdgit clone --depth 1 https://github.com/payloadcms/payloadWrote 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/commands/payloadcms/payload/analyze-issue)<a href="https://agentmods.dev/commands/payloadcms/payload/analyze-issue"><img src="https://agentmods.dev/badge/commands/payloadcms/payload/analyze-issue/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/commands/payloadcms/payload/analyze-issue"><img src="https://agentmods.dev/badge/commands/payloadcms/payload/analyze-issue.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.00010 | $0.00361 |
| Opus 5.5 | $0.00004 | $0.00144 |
| Sonnet 5.5 | $0.00002 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
analyze-issue 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 1mo 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
Deep-dive on the GitHub issue provided in $ARGUMENTS. Find the problem and generate a plan. Do not write code. Explain the problem clearly and propose a comprehensive plan to solve it.
PROMPT for the issue number or URL if not provided, and stop here.
Steps:
- Fetch issue data using:
gh issue view $ARGUMENTS --json author,title,number,body,comments,labels - Parse the JSON response to extract:
- Title and number
- Description (body)
- All comments with authors
- Labels
- Format the issue context clearly
- Review the issue context and details
- Examine the relevant parts of the codebase. Analyze the code thoroughly until you have a solid understanding of how it works.
- Explain the issue in detail, including the problem and its root cause. There is no guarantee the issue is valid, so be critical and thorough in your analysis.
- Create a comprehensive plan to solve the issue. The plan should include:
- Required code changes
- Potential impacts on other parts of the system
- Necessary tests to be written or updated
- Documentation updates
- Performance considerations
- Security implications
- Backwards compatibility (if applicable)
- Include the reference link to the source issue and any related discussions
- Think deeply about all aspects of the task. Consider edge cases, potential challenges, and best practices for addressing the issue.
IMPORTANT: ONLY CREATE A PLAN. DO NOT WRITE ANY CODE. Your task is to create a thorough, comprehensive strategy for understanding and resolving the 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.
- 1mo ago First seen · 34 lines · 10 tokens per session scan A 3cf0141be012
analyze-issue is a command published in the GitHub repository payloadcms/payload (45,565 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 361 once invoked, about $0.0000 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 commands, from other repositories
dev-fix
Unified developer workflow for fixing bugs. Analyzes issue-tracker context, cross-checks docs/code, proposes a solution, implements the fix, verifies locally, and delivers a PR/MR.
health
One-line reliability verdict (OK / DEGRADED / FAILING) for Claude Code usage.
codebase-review
Review an entire codebase for architecture, engineering health, and exploitable risk; generate a prioritized remediation plan, an evidence-anchored system knowledge document, or both.
implement-feature
Implement an approved feature plan with benefit-based placement, TDD, revision-bound evidence, and PR-ready output.
fix-issue
Analyze and fix a GitHub issue end-to-end.
prepare-release
Release readiness review with project-steward (commits, version sync, changelog, updater).