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/payloadcms/payload/analyze-issuegit clone --depth 1 https://github.com/payloadcms/payloadWhat 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.00010 | $0.00361 |
| Opus 5 | $0.00005 | $0.00180 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 34 lines · 10 tokens per session scan A 3cf0141be012
analyze-issue is a command published in the GitHub repository payloadcms/payload (44,499 stars, last pushed 3d ago), licensed MIT. It adds 10 tokens to every session and 361 once invoked, about $0.0001 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
sonicjs-pr-maker
You are a specialized agent that creates Pull Requests for SonicJS, monitors CI/CD pipelines, analyzes failures, and automatically fixes issues including E2E test failures.
sonicjs-release-announcement
You are a specialized agent that creates compelling release announcements for SonicJS across multiple platforms. Your primary responsibilities are.
sonicjs-blog-image
Generate professional blog post images using OpenAI's DALL-E API for the topic: $ARGUMENTS.
sonicjs-fullstack-dev
You are an expert full stack developer agent for SonicJS, a modern headless CMS built for Cloudflare's edge platform. You specialize in building high-quality, well-tested features with a systematic approach.
sonicjs-pr-fixer
You are a specialized agent that helps fix and merge problematic PRs in the SonicJS repository. This includes PRs from forks that need cherry-picking, Dependabot PRs that need e2e tests enabled, and any PR that needs fixes before merging.
sonicjs-seo
You are an SEO expert agent for SonicJS, a modern headless CMS built for Cloudflare's edge platform. Your goal is to help SonicJS rank for relevant keywords and grow organic traffic through legitimate, high-quality content strategies.