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 gantt-schedulinggit 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/gantt-scheduling)<a href="https://agentmods.dev/skills/perforce/p4plan-mcp/gantt-scheduling"><img src="https://agentmods.dev/badge/skills/perforce/p4plan-mcp/gantt-scheduling.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.00051 | $0.00482 |
| Opus 5 | $0.00026 | $0.00241 |
| Sonnet 5 | $0.00010 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
p4-plan-gantt-scheduling 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 7d 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.
Gantt Scheduling in P4 Plan
P4 Plan supports Gantt scheduling for traditional project planning with timelines and task dependencies. Scheduled tasks live in the Planning section.
Key Concepts
- Scheduled task: A time-boxed item with start date, finish date, duration, and optional dependencies.
- Dependency types: End-to-Start (most common), Start-to-Start, End-to-End, Start-to-End.
- Percent complete: Progress tracking (0-100). Setting to 100 auto-completes.
- Estimated days: Effort estimate (can differ from calendar duration).
- Planning items include ScheduledTask, Sprint, and Release types.
Tool Mapping
| User Intent | Tool | Key Parameters |
|---|---|---|
| Create scheduled task | create_item | type: "scheduled_task", projectId, name, estimatedDays, start, finish |
| Create sub-task | create_item | type: "scheduled_task", projectId, name, parentItemId |
| Insert after an item | create_item | type: "scheduled_task", projectId, name, previousItemId |
| Find planning items | search_tasks | findQuery, projectId |
| Get task details (dates, deps) | get_tasks | taskIds |
| Update progress | update_item | itemId, percentCompleted |
| Update effort estimate | update_item | itemId, estimatedDays |
| Assign to user | update_item | itemId, assignedTo: [{ userID }] |
| Start task | start_task | taskId |
| Complete task | complete_task | taskId |
| Get team members | 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.
- 7d ago First seen · 37 lines · 51 tokens per session scan A 01984112ff51
p4-plan-gantt-scheduling is a skill published in the GitHub repository perforce/p4plan-mcp (4 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 482 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
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"…
log-activity
Log calls, meetings, notes, and other activities to CRM item timelines — structured records with attendees, outcomes, and follow-ups. Use when someone says "log my call with", "add a note to the deal", "what activities happened on", "record this meeting", "update my note on", "track a call with", "log a meeting with"…
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…
pipefy-pipes-and-cards
Use this skill when the user wants to read, create, update, or delete pipes, phases, phase fields, labels, cards, comments, or field conditions. Covers 40 MCP tools for the core pipe and card lifecycle. Use the seed-pipe-across-phases workflow when populating empty phases for demos or QA.
pipefy-process-design
Use this skill ONLY when the user explicitly asks for help designing or architecting a process ("help me design", "what's the best structure", "how do I organize this flow?"). For direct execution requests ("create a pipe for X", "build a reimbursement process", or any message with a detailed spec), skip this skill…