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/ondrasek/cc-plugins/managenpx skills add ondrasek/cc-plugins --skill managegit clone --depth 1 https://github.com/ondrasek/cc-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.00025 | $0.01082 |
| Opus 5 | $0.00013 | $0.00541 |
| Sonnet 5 | $0.00005 | $0.00216 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
manage 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 yesterday.
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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage
Modifies existing issues — edit, close, reopen, delete, batch operations, and label management.
For creating new issues, use /github-issues:create.
Critical Rules
- Read cross-cutting behaviors first:
skills/shared/references/cross-cutting.md - Always add a comment when making significant changes (labels, milestone, assignee)
- Always preview before making major edits
- NEVER create priority labels — see
skills/shared/references/label-taxonomy.md - Use
--jsonflags for structured output
Prerequisites Check
gh auth status
Review Before Modifying
Before executing any issue edit (title, body, labels, assignee, milestone), delegate to the issue-reviewer agent to validate the proposed changes. Present the review results to the user. If the review fails, fix the issues before proceeding.
Capabilities
1. Edit Issue
Modify issue properties with context.
# Edit title
gh issue edit NUMBER --title "New title"
# Edit body
gh issue edit NUMBER --body "New body"
# Add labels
gh issue edit NUMBER --add-label "bug"
# Remove labels
gh issue edit NUMBER --remove-label "chore"
# Set assignee
gh issue edit NUMBER --add-assignee USERNAME
# Remove assignee
gh issue edit NUMBER --remove-assignee USERNAME
# Set milestone
gh issue edit NUMBER --milestone "v2.0"
Always add a comment explaining the change:
gh issue comment NUMBER --body "Updated labels: added \`bug\` — this is a defect in existing behavior, not a missing feature."
3. Close Issue
Workflow:
- View the issue — understand what's being closed
- Check for dependents — search for issues referencing this one:
gh issue list --search "#NUMBER" --state open --json number,title - Close with reason:
# Completed gh issue close NUMBER --reason completed --comment "Resolved by #PR or description of resolution" # Not planned gh issue close NUMBER --reason "not planned" --comment "Reason for not proceeding" - Notify dependents — if other issues reference this one, comment on them:
gh issue comment DEPENDENT_NUMBER --body "Note: #NUMBER has been closed. Impact on this issue: ..."
What ships with it
1 file 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.
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.
- yesterday First seen · 152 lines · 25 tokens per session scan A 5dcde7384913
manage is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,082 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
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.