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 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/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/search-queries"><img src="https://agentmods.dev/badge/skills/perforce/p4plan-mcp/search-queries.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.00048 | $0.03914 |
| Opus 5.5 | $0.00019 | $0.01566 |
| Sonnet 5.5 | $0.00010 | $0.00783 |
| Haiku 4.5 | $0.00005 | $0.00391 |
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 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 — 355 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.
- 2d ago Changed 0d0b46013842
- 1mo ago Changed · +70 lines 043ad6bc748f
- 1mo 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 3d ago), licensed MIT. It adds 48 tokens to every session and 3,914 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
daily-briefing
Start your day with a prioritized CRM briefing — works for any monday CRM setup: pipeline, contacts, accounts, leads, or no board at all. Use when someone says 'morning briefing', 'daily brief', 'what's on my plate today', 'catch me up on my deals', 'what needs attention', 'what needs my attention', 'anything urgent…
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…
Technical Debt Tracking with PMAT
Tracks and manages technical debt using PMAT (Pragmatic AI Labs MCP Agent Toolkit). Use this skill when: User asks about technical debt, TODO comments, or code quality issues Planning sprint work and need to prioritize debt repayment Conducting code audits or technical debt assessments Tracking debt accumulation…
getting-started
Connect Taskade and show the user what they can do with it. Use when the user says "set up Taskade", "connect Taskade", "what can you do in Taskade", "what is in my Taskade workspace", or when a Taskade tool fails with a sign-in or plan error.
p4-dam-workflows
P4 DAM (Digital Asset Management) workflows — search, browse, tag, review, and manage digital assets via P4 MCP tools. Use when discovering, searching, filtering, reviewing, or managing assets stored in P4 DAM.
continue-project
Find the user's saved Glif project, show its media, and add new work to it without starting a separate project. Use when: "show my recent Glif projects", "open my last image", "keep going on that one", "make 5 variations to A/B test", "same but vertical", "make a version for TikTok", "resize it to every format", "same…