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 skills/perforce/p4plan-mcp/bug-trackingnpx skills add perforce/p4plan-mcp --skill bug-trackinggit clone --depth 1 https://github.com/perforce/p4plan-mcpWhat 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.00054 | $0.00496 |
| Opus 5 | $0.00027 | $0.00248 |
| Sonnet 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 2d 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.
- 2d 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 3mo ago), licensed MIT. It adds 54 tokens to every session and 496 once invoked, about $0.0003 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-31.
Other skills, from other repositories
p4-code-review
P4 code review workflows — discover, create, vote, comment, transition, and manage reviews via P4 MCP tools. Use when: creating reviews, voting, commenting, transitioning review states, managing participants, or tracking review activity in P4.
p4-file-operations
P4 file operations — query content, history, annotations, diffs, and modify files (add, edit, delete, move, sync, resolve) via P4 MCP tools. Use when: reading file content, viewing history, comparing revisions, adding or editing files, syncing, resolving conflicts, or reconciling workspace changes in P4.
p4-stream-workflows
P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools. Use when: creating streams, branching, merging, copying between streams, integrating changes, switching workspaces, or managing stream specs in P4.
p4-changelist-management
P4 changelist workflows — create, list, submit, shelve, unshelve, and manage changelists and shelved files via P4 MCP tools. Use when: creating changelists, editing files, shelving, unshelving, submitting, organizing changes, or managing pending work in P4.
p4-workspace-setup
P4 workspace setup and management — create, configure, sync, and switch workspaces via P4 MCP tools. Use when: creating workspaces, configuring client specs, syncing files, switching workspaces, or checking workspace status in P4.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.