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 creategit 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/create)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/create"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/create/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/create"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/create.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.00058 | $0.01540 |
| Opus 5.5 | $0.00023 | $0.00616 |
| Sonnet 5.5 | $0.00012 | $0.00308 |
| Haiku 4.5 | $0.00006 | $0.00154 |
Grade A, and why
create 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create
Creates a new GitHub issue from a rough idea, immediately refining it into a well-structured issue with deep research.
Critical Rules
- Read cross-cutting behaviors first:
skills/shared/references/cross-cutting.md - Research before writing — use every available tool to gather context
- Always search for duplicates before creating
- Always preview the issue with the user before submitting
- NEVER create priority labels — see
skills/shared/references/label-taxonomy.md - Add a creation comment summarizing research sources and decisions
Prerequisites Check
gh auth status
If this fails, tell the user to run gh auth login first.
Workflow
Phase 1: Understand the Intent
Parse the user's request. Identify:
- Is this a bug report, feature request, task, or something else?
- What problem does it solve or what value does it add?
- Are there specific details (error messages, file paths, steps to reproduce)?
Phase 2: Deep Research
Use every available tool to gather as much context as possible. The goal is to create an issue that is immediately actionable — not a placeholder.
2a. Codebase Research
Scan the local codebase for relevant context:
- Search for related code — find files, functions, classes related to the issue topic
- Read relevant files — understand the current implementation
- Check for TODOs/FIXMEs — existing markers for known issues
- Review recent commits — has this area been recently changed?
# Recent changes in relevant area
git log --oneline -20 -- "path/to/area"
2b. Web Research
Search the web for relevant context — this is critical for well-informed issues:
- Error messages — search for exact error text to find known issues, solutions
- Library/framework issues — check upstream bug trackers for related problems
- Best practices — search for recommended approaches to the problem
- Documentation — find official docs for relevant APIs, libraries, tools
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 · 224 lines · 58 tokens per session scan A 57cd67356178
create is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,540 once invoked, about $0.0002 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…