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 ondrasek/cc-plugins --skill managegit clone --depth 1 https://github.com/ondrasek/cc-pluginsWrote 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/ondrasek/cc-plugins/manage)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/manage"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/manage/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/ondrasek/cc-plugins/manage"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/manage.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.01082 |
| Opus 5.5 | $0.00010 | $0.00433 |
| Sonnet 5.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 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 — 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.
- 1mo ago 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 5mo 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.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…