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/search-queriesnpx skills add perforce/p4plan-mcp --skill search-queriesgit 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/search-queries)<a href="https://agentmods.dev/skills/perforce/p4plan-mcp/search-queries"><img src="https://agentmods.dev/badge/skills/perforce/p4plan-mcp/search-queries.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.1 | $0.00048 | $0.03121 |
| Opus 5 | $0.00024 | $0.01561 |
| Sonnet 5 | $0.00010 | $0.00624 |
| Haiku 4.5 | $0.00005 | $0.00312 |
Grade A, and why
p4-plan-search-queries 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 5d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
P4 Plan Find Query Syntax
The search_tasks tool accepts a findQuery parameter for searching using P4 Plan's query language. Use it to filter by status, assignee, priority, dates, or any combination. For simple name search use Itemname:Text("text").
⚠️ Column names must be spelled exactly as shown below. There is no priority column — use Productbacklogpriority, Sprintpriority, or Bugpriority. There is no itemType — use Itemtype. No spaces in column names, exact casing. Values use human-readable strings like "Very high priority", NOT enum values like "veryHigh".
Common Mistakes
| ❌ Wrong | ✅ Correct |
|---|---|
itemType="Bug" |
Itemtype="Bug" |
priority="veryHigh" |
Productbacklogpriority="Very high priority" |
Bugpriority="veryHigh" |
Bugpriority="Very high priority" |
type="Bug" |
Itemtype="Bug" |
assignedTo:Resource("john") |
Assignedto:Resource("john") |
itemName:Text("login") |
Itemname:Text("login") |
status = "notDone" (spaces around =) |
Status="Not done" (no spaces around =) |
Status="notDone" |
Status="Not done" (use human-readable text) |
Severity="high" |
Severity="A" (A/B/C/D letter codes) |
Severity="Critical" |
Severity="A" (use letter codes, not text names) |
Operators
| Operator | Meaning | Example |
|---|---|---|
AND or + |
Both conditions true | Status="Not done" AND Severity="A" |
OR |
Either condition true | Status="Not done" OR Status="In progress" |
NOT or ! |
Negate condition | NOT Status="Completed" |
- |
First true, second not | Status="Not done" - Workremaining>5 |
() |
Group conditions | (Severity="A" OR Severity="B") AND Status="Not done" |
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.
- 5d ago First seen · 285 lines · 48 tokens per session scan A 826a00d2f9fc
p4-plan-search-queries is a skill published in the GitHub repository perforce/p4plan-mcp (4 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 3,121 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-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-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-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…