Borrowing it
Nothing to install: this file belongs to prolific-oss/cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/prolific-oss/cli/main/.claude/skills/cli-command-create/SKILL.mdgit clone --depth 1 https://github.com/prolific-oss/cliWrote 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/prolific-oss/cli/cli-command-create)<a href="https://agentmods.dev/skills/prolific-oss/cli/cli-command-create"><img src="https://agentmods.dev/badge/skills/prolific-oss/cli/cli-command-create.svg" alt="Measured on agentmods" 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.00020 | $0.01408 |
| Opus 5 | $0.00010 | $0.00704 |
| Sonnet 5 | $0.00004 | $0.00282 |
| Haiku 4.5 | $0.00002 | $0.00141 |
Grade A, and why
cli-command-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 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Command Creator
When to Use This Skill
Invoke this skill when the user:
- Asks to "create a command", "add a command", or "implement a command" for the CLI
- Mentions adding new CLI functionality (e.g., "create me a command that publishes collections")
- Uses the slash command /cli-command-create
Create a new CLI command for the Prolific CLI from start to finish.
Arguments
Arguments may be provided via $ARGUMENTS or gathered interactively.
Expected arguments:
ticket- Jira ticket number (e.g., DCP-2154)resource- Resource name (e.g., collection, study, workspace)command- Command name (e.g., list, get, create, update)command-type- Optional: LIST | VIEW | CREATE | UPDATE | ACTION (will infer if not provided)
If arguments are missing or $ARGUMENTS is empty, use the AskUserQuestion tool to gather them:
- First ask for the Jira ticket number (e.g., "DCP-2154")
- Then ask for the resource name (e.g., "collection", "study", "workspace")
- Then ask for the command name (e.g., "list", "get", "create", "publish")
- Finally ask for the command type with options: LIST, VIEW, CREATE, UPDATE, ACTION (or let Claude infer from the command name)
Phase 1: Gather Requirements
1.1 Understand the API Contract
Ask the user to provide ONE of:
- Bruno file path - e.g.,
path/to/request.bru - Inline API contract - endpoint, request/response examples, error codes
Also ask if they have any acceptance criteria (optional):
- Feature requirements or user stories
- Expected behavior descriptions
- Edge cases to handle
1.2 Determine Command Type
If not provided, infer from command name:
list→ LIST (paginated results, multiple renderers)get,view→ VIEW (single resource, one renderer)create→ CREATE (accepts template file)update→ UPDATE (modifies existing resource)- Other → ACTION (state transitions, operations)
1.3 Identify Required Flags
Based on command type, confirm which flags are needed:
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 · 175 lines · 20 tokens per session scan A afc76b7c5f46
cli-command-create is a skill published in the GitHub repository prolific-oss/cli (13 stars, last pushed 3d ago), licensed Apache-2.0. It adds 20 tokens to every session and 1,408 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.