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/project-navigationnpx skills add perforce/p4plan-mcp --skill project-navigationgit 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/project-navigation)<a href="https://agentmods.dev/skills/perforce/p4plan-mcp/project-navigation"><img src="https://agentmods.dev/badge/skills/perforce/p4plan-mcp/project-navigation.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00527 |
| Opus 5 | $0.00023 | $0.00264 |
| Sonnet 5 | $0.00009 | $0.00105 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
p4-plan-project-navigation 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 3d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Navigation in P4 Plan
Key Concepts
Every project has three sections, each with a different ID:
| Section | Contains | ID Source |
|---|---|---|
| Planning | Sprints, ScheduledTasks, Releases | project.id (same as project ID) |
| Backlog | BacklogTasks, User Stories | project.backlogID |
| QA | Bugs | project.qaID |
Call get_project(projectId) to retrieve backlogID and qaID. Most tools accept the project ID directly and resolve the correct section internally.
Filter Values Quick Reference
Status: notDone, inProgress, completed, blocked Backlog priority: veryHigh, high, medium, low, veryLow, none Bug severity: A (critical), B (high), C (medium), D (low), none
Tool Mapping
| User Intent | Tool | Key Parameters |
|---|---|---|
| List all projects | list_projects | (none) |
| Get project details + section IDs | get_project | projectId |
| Get current user info | get_current_user | (none) |
| List project team members | list_project_users | projectId |
| See my assigned work (To Do List) | get_my_tasks | showCompleted, showOnlyNextFourWeeks, showPipelineTasksThatCannotStart |
| Search by name | search_tasks | findQuery, projectId, limit |
| Get any item's full details | get_tasks | taskIds |
| Read custom field values | get_custom_fields | taskId, onlySet |
Typical Starting Sequence
- list_projects() -- find the project
- get_project(projectId) -- get section IDs
- Use search_tasks or get_my_tasks to find items, then get_tasks for details
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.
- 3d ago First seen · 49 lines · 46 tokens per session scan A b99f34d75435
p4-plan-project-navigation is a skill published in the GitHub repository perforce/p4plan-mcp (4 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 527 once invoked, about $0.0002 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.
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…