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 tjboudreaux/cc-plugin-perforce --skill tools-p4-shelvinggit clone --depth 1 https://github.com/tjboudreaux/cc-plugin-perforceWrote 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/tjboudreaux/cc-plugin-perforce/tools-p4-shelving)<a href="https://agentmods.dev/skills/tjboudreaux/cc-plugin-perforce/tools-p4-shelving"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-perforce/tools-p4-shelving/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/tjboudreaux/cc-plugin-perforce/tools-p4-shelving"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-perforce/tools-p4-shelving.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.00025 | $0.02343 |
| Opus 5 | $0.00013 | $0.01171 |
| Sonnet 5 | $0.00005 | $0.00469 |
| Haiku 4.5 | $0.00003 | $0.00234 |
Grade A, and why
tools-p4-shelving 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 10d 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 — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perforce Shelving
Overview
Shelving stores pending changes on the Perforce server without submitting them. This enables code review, work-in-progress backup, sharing between workspaces, and collaboration.
When to Use
- Backing up work-in-progress
- Sharing changes for code review
- Switching between tasks
- Transferring work between workspaces
- Parking changes temporarily
- Pre-submit review (Swarm)
Core Concepts
Shelving vs Submitting
| Feature | Shelving | Submitting |
|---|---|---|
| Stored on server | Yes | Yes |
| Creates revision | No | Yes |
| Visible to others | Yes (optional) | Yes |
| Reversible | Easy delete | Need revert |
| Affects depot | No | Yes |
| Builds triggered | Usually no | Usually yes |
Basic Shelving
Shelve Changes
# Shelve all files in changelist
p4 shelve -c 12345
# Shelve specific files
p4 shelve -c 12345 file1.txt file2.txt
# Shelve and keep files open
p4 shelve -c 12345
# Shelve default changelist
p4 shelve
# Replace existing shelf
p4 shelve -f -c 12345
# Shelve with delete of local files (submit-like)
p4 shelve -c 12345
p4 revert -c 12345 //...
View Shelved Changes
# List shelved changelists
p4 changes -s shelved
# List your shelved changelists
p4 changes -s shelved -u $P4USER
# Describe shelved changelist
p4 describe -S 12345
# List files in shelf
p4 describe -S -s 12345
# Diff shelved file vs depot
p4 diff2 //depot/file.txt //depot/file.txt@=12345
Unshelve Changes
# Unshelve to same changelist
p4 unshelve -s 12345
# Unshelve to different changelist
p4 unshelve -s 12345 -c 12346
# Unshelve to new changelist
p4 unshelve -s 12345 -c default
# Then move to new CL if desired
# Unshelve specific files
p4 unshelve -s 12345 file.txt
# Force unshelve (overwrite local changes)
p4 unshelve -s 12345 -f
Delete Shelf
# Delete shelved files from changelist
p4 shelve -d -c 12345
# Delete specific files from shelf
p4 shelve -d -c 12345 file.txt
# Delete shelf completely
p4 shelve -d -c 12345 //...
# Promote shelf to commit (delete shelf after submit)
p4 submit -e 12345
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.
- 10d ago First seen · 385 lines · 25 tokens per session scan A 99261b54d0c8
tools-p4-shelving is a skill published in the GitHub repository tjboudreaux/cc-plugin-perforce (8 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 2,343 once invoked, about $0.0001 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.