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/p47phoenix/claude-plugins/operationsnpx skills add P47Phoenix/Claude-Plugins --skill operationsgit clone --depth 1 https://github.com/P47Phoenix/Claude-PluginsWhat 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.00109 | $0.02208 |
| Opus 5 | $0.00055 | $0.01104 |
| Sonnet 5 | $0.00022 | $0.00442 |
| Haiku 4.5 | $0.00011 | $0.00221 |
Grade A, and why
operations 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operations Agent
Design Principle: Role Context Isolation
This skill keeps operations-specific knowledge out of the main context window. When an operations task is requested, the relevant role is detected, only the corresponding reference file(s) are loaded, and a sub-agent is spawned with that isolated context. The main context receives only the finished operations artifact.
Unlike simple single-reference skills, operations tasks frequently span concerns -- a release may need Release Manager planning and Technical Writer release notes simultaneously. This skill follows the godot pattern: multiple overlapping references loaded into a single sub-agent when the task warrants it.
Phase 1: Role Detection
Detect the relevant operations role(s) from (in priority order):
- Explicit role mention -- "as a DevOps engineer", "release manager perspective", "technical writer"
- Task type signals -- see role manifests below
- Domain signals -- infrastructure/pipeline keywords route to DevOps; release/versioning keywords route to Release Manager; documentation/guide keywords route to Technical Writer
- Scope signals -- build/deploy automation --> DevOps; release coordination/planning --> Release Manager; content creation/documentation --> Technical Writer
If ambiguous, ask before proceeding. Do not assume.
Declare before every task:
Role: [ROLE] | Task: [TYPE] | References: [list of reference files]
Role Routing Table
Load only the matched role manifest. Each manifest contains the full task-type routing table, instructions, and guardrails for that role.
| Role | Manifest | Detection Cue |
|---|---|---|
| DevOps | references/roles/devops.md |
CI/CD / deployment / infra / monitoring / incident / capacity |
| Release Manager | references/roles/release-manager.md |
release plan / version / rollback / feature flag / go-no-go |
| Technical Writer | references/roles/technical-writer.md |
API docs / user guide / runbook / release notes / docs plan |
What ships with it
19 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/api-documentation.md 9.6 KB
- references/ci-cd-patterns.md 9.8 KB
- references/contracts/cross-role-tasks.md 1.3 KB
- references/contracts/devops-output.md 854 B
- references/contracts/release-manager-output.md 652 B
- references/contracts/technical-writer-output.md 708 B
- references/deployment-strategies.md 11 KB
- references/documentation-standards.md 12 KB
- references/feature-flag-patterns.md 11 KB
- references/infrastructure-patterns.md 11 KB
- references/observability.md 12 KB
- references/release-planning.md 8.9 KB
- references/roles/devops.md 3.3 KB
- references/roles/release-manager.md 2.9 KB
- references/roles/technical-writer.md 3.0 KB
- references/rollback-strategies.md 11 KB
- references/runbook-templates.md 11 KB
- references/user-guides.md 9.9 KB
- references/versioning-patterns.md 8.5 KB
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 First seen · 220 lines · 109 tokens per session scan A 81499610329a
operations is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 109 tokens to every session and 2,208 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…