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/p4mcp-server/p4-stream-workflowsnpx skills add perforce/p4mcp-server --skill p4-stream-workflowsgit clone --depth 1 https://github.com/perforce/p4mcp-serverWrote 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/p4mcp-server/p4-stream-workflows)<a href="https://agentmods.dev/skills/perforce/p4mcp-server/p4-stream-workflows"><img src="https://agentmods.dev/badge/skills/perforce/p4mcp-server/p4-stream-workflows.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.00061 | $0.01092 |
| Opus 5 | $0.00030 | $0.00546 |
| Sonnet 5 | $0.00012 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
p4-stream-workflows 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 4d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stream Workflows
Use the query_streams and modify_streams tools to manage P4 streams.
Querying Streams
| Action | Purpose | Key Parameters |
|---|---|---|
list |
List streams under a depot path | stream_path, filter, fields, max_results |
get |
Get a single stream spec | stream_name |
children |
List child streams | stream_name |
parent |
Get parent stream | stream_name |
graph |
Get full stream hierarchy | stream_path |
integration_status |
Check pending integrations between stream and parent | stream_name, both_directions, force_refresh |
get_workspace |
Get workspace bound to a stream | stream_name, workspace |
list_workspaces |
List all workspaces for a stream | stream_name, user |
validate_file |
Check if a file path is valid in a stream | stream_name, file_paths, workspace |
validate_submit |
Verify a changelist is ready to submit in stream context | workspace, changelist |
check_resolve |
Check if resolve is needed after integration | stream_name |
interchanges |
List changes not yet integrated between stream and parent | stream_name, reverse, limit |
Modifying Streams
| Action | Purpose | Key Parameters |
|---|---|---|
create |
Create a new stream | stream_name, stream_type, parent, description |
update |
Update stream spec fields | stream_name, updated fields |
delete |
Delete a stream (requires approval) | stream_name |
edit_spec |
Open stream spec for editing | stream_name, changelist |
resolve_spec |
Resolve spec conflicts | stream_name, resolve_mode |
revert_spec |
Revert spec changes | stream_name |
shelve_spec |
Shelve stream spec changes | stream_name, changelist |
unshelve_spec |
Unshelve stream spec changes | stream_name, target_changelist |
Stream Propagation (Branching & Merging)
| Action | Purpose | Key Parameters |
|---|---|---|
copy |
Copy changes between parent/child streams | stream_name, changelist, parent_stream |
merge |
Merge changes between parent/child streams | stream_name, changelist, parent_stream |
integrate |
Integrate with custom source/target (advanced) | stream_name, changelist, parent_stream |
populate |
Seed a new stream with files from parent | stream_name |
switch |
Switch a workspace to a different stream | stream_name, workspace |
create_workspace |
Create a workspace bound to a stream | stream_name, workspace_name, root |
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.
- 4d ago First seen · 85 lines · 0 tokens per session scan A 24160c002b71
p4-stream-workflows is a skill published in the GitHub repository perforce/p4mcp-server (114 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 1,092 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-30.
Other skills, from other repositories
p4-plan-search-queries
P4 Plan Find query syntax for advanced searching. Use when user needs to search, filter, or find items by status, assignee, priority, severity, dates, custom fields, or any combination.
p4-plan-comment-html-format
Author HTML-formatted comments and multiline field values that render correctly in both the Qt desktop client and the React web client. Use when posting/editing comments, setting Multiline Text custom fields, or writing detailedDescription/stepsToReproduce on a Bug.
p4-plan-mentions
Format @user mentions inside HTML comments and multiline fields so they render as a proper link in both the Qt desktop client and the React web client. Use when the user wants to ping someone, notify a teammate, address @-name, or reference a user inside a comment / description / steps to reproduce.
p4-plan-task-management
Manage tasks, status updates, assignments, comments, and attachments in P4 Plan. Use when user mentions tasks, status, updates, assignments, my work, todo list, assign, comments, attachments, or collaboration.
p4-plan-planning
Manage sprints, releases, and sprint commitment in P4 Plan. Use when user mentions sprints, sprint planning, capacity, velocity, committing work, iterations, burndown, releases, milestones, versions, or tagging.
p4-plan-backlog-refinement
Guide backlog refinement sessions, story refinement, estimation, and prioritization in P4 Plan. Use when user mentions backlog, refinement, estimation, story points, or prioritization.