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/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/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/p4mcp-server/p4-stream-workflows"><img src="https://agentmods.dev/badge/skills/perforce/p4mcp-server/p4-stream-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.01092 |
| Opus 5.5 | $0.00000 | $0.00437 |
| Sonnet 5.5 | $0.00000 | $0.00218 |
| Haiku 4.5 | $0.00000 | $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 1mo 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.
- 1mo 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 (122 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,092 tokens. 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
github-via-nyxid
Operate a user's GitHub account through NyxID's credential-brokering proxy (service slug api-github) — read and write repositories, files, issues, pull requests, commits, branches, Actions, gists and anything else the GitHub REST API exposes, all on the user's behalf and without ever handling a raw token. NyxID…
git-workflow
Git best practices for version control and collaboration.
issue-management
Create, update, list and search GitHub issues and PRs, list a repository's labels, run milestones, and check for duplicates.
setup-ci
Set up CI for a project, and offer to generate its own /release skill. Detects the stack, writes .github/workflows/ci.yml from the guide's baseline and generates the project's own .claude/skills/release/SKILL.md (release process: version bump, tag, CI watch, registry check). Use when the user says "set up CI", "add a…
release-versioning
Discipline for release classification, version bumps, and changelogs, Conventional Commits classify the release range, SemVer computes the version from those commits, Keep a Changelog renders the result. Use when the user asks to cut a release, bump a version, write a changelog, decide if a change is a…
repository-manager-concept-coordination
Reserve, inspect, release, and materialize a CONCEPT:ID claim, and verify a candidate's or generation's introduced concept markers against those claims, via the repository-manager rmconcepts MCP tool / --concepts CLI family. Routes agents away from hand-writing a CONCEPT: marker without first reserving its id, which…