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 skills add perforce/p4plan-mcp --skill bug-trackinggit clone --depth 1 https://github.com/perforce/p4plan-mcpWrote 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/perforce/p4plan-mcp/bug-tracking)<a href="https://agentmods.dev/skills/perforce/p4plan-mcp/bug-tracking"><img src="https://agentmods.dev/badge/skills/perforce/p4plan-mcp/bug-tracking/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/perforce/p4plan-mcp/bug-tracking"><img src="https://agentmods.dev/badge/skills/perforce/p4plan-mcp/bug-tracking.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.00054 | $0.00496 |
| Opus 5.5 | $0.00022 | $0.00198 |
| Sonnet 5.5 | $0.00011 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
p4-plan-bug-tracking 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.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Tracking in P4 Plan
Bugs are tracked in the Quality Assurance section. Use the project's qaID (from get_project) when creating bugs.
Key Concepts
- Severity: A (critical/system unusable), B (major functionality broken), C (partially working), D (minor/cosmetic)
- Bug fields: name, severity, detailedDescription, stepsToReproduce, priority
- Bug priority values: veryHigh, high, medium, low, veryLow, none (separate from severity)
- Bugs can be committed to sprints and tagged to releases just like backlog items.
Tool Mapping
| User Intent | Tool | Key Parameters |
|---|---|---|
| Create a bug | create_item | type: "bug", projectId, name, severity, detailedDescription, stepsToReproduce |
| Find bugs | search_tasks | findQuery, projectId (use QA section ID) |
| Get bug details | get_tasks | taskIds |
| Set severity | update_item | itemId, severity (A/B/C/D) |
| Set priority | update_item | itemId, priority |
| Assign bug | update_item | itemId, assignedTo: [{ userID }] |
| Start work on bug | start_task | taskId |
| Resolve bug | complete_task | taskId |
| Add discussion | post_comment | taskId, text |
| List attached files | get_attachments | taskId |
| View screenshot/file | download_attachment | taskId, path (from get_attachments) |
| Commit bug to sprint | commit_to_sprint | taskId, sprintId |
| Get team for assignment | list_project_users | projectId |
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 · 37 lines · 54 tokens per session scan A d23c6a146d00
p4-plan-bug-tracking is a skill published in the GitHub repository perforce/p4plan-mcp (4 stars, last pushed 17d ago), licensed MIT. It adds 54 tokens to every session and 496 once invoked, about $0.0002 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-31.
Other skills, from other repositories
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
bug-triage
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…