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/iris-hep/marketplace/cli-creatornpx skills add iris-hep/marketplace --skill cli-creatorgit clone --depth 1 https://github.com/iris-hep/marketplaceWrote 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/iris-hep/marketplace/cli-creator)<a href="https://agentmods.dev/skills/iris-hep/marketplace/cli-creator"><img src="https://agentmods.dev/badge/skills/iris-hep/marketplace/cli-creator.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 | $0.00071 | $0.00755 |
| Opus 5 | $0.00036 | $0.00378 |
| Sonnet 5 | $0.00014 | $0.00151 |
| Haiku 4.5 | $0.00007 | $0.00076 |
Grade A, and why
cli-creator 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cli Creator
Overview
Create a Python CLI module and expose it via pyproject.toml console scripts while matching existing project conventions.
Workflow
0) Initialize an empty directory (only when no package exists)
- If the working directory is empty or lacks a Python package, bootstrap a new project:
- Create a Python 3.13 virtual environment with uv (default).
- Install Hatch in the venv.
- Use Hatch to create an empty package; set the package name to the CLI name.
- Ensure
pyproject.tomlis created by Hatch and reflects the package name.
- After initialization, continue with the workflow below.
Commands to run (replace my-cli with the desired name):
uv venv --python 3.13 .venv
source .venv/bin/activate
uv pip install hatch
hatch new my-cli
1) Inspect project layout
- Read
pyproject.tomlto detect packaging style ([project], [tool.poetry], [tool.hatch], existing scripts). - Locate the package layout (
src/vs flat) and any existing CLI modules or patterns.
2) Choose a CLI framework
- Use Typer. Reuse existing Typer patterns in the repo when present.
3) Gather command structure
- Ask for the top-level command name and at least one subcommand name.
- Prefer a concrete example command line (e.g.,
atlas-trigger dataset list) to infer subcommands and nesting. - If the user only provides one subcommand, still structure the CLI with that subcommand.
- Ask whether the command handlers should delegate to another module for the "meat" of the logic.
- If the user wants delegation, import the target module inside the command function so
--helpremains fast.
4) Implement the CLI module
- Create a module under the package that defines a
main()entry point (returning an exit code). - Keep side effects out of module import; parsing and execution should happen in
main(). - For Typer, define
app = typer.Typer()and invokeapp()insidemain()or usetyper.run(main)for single-command CLIs. - Implement the requested command(s) with dummy handlers that print
hello from <command>using the full command path (e.g.,hello from atlas-trigger dataset list).
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.
- 4d ago First seen · 73 lines · 71 tokens per session scan A 23dfbc8de4d5
cli-creator is a skill published in the GitHub repository iris-hep/marketplace (4 stars, last pushed 28d ago), licensed BSD-3-Clause. It adds 71 tokens to every session and 755 once invoked, about $0.0004 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
bump-dependency
Bumps a Python package dependency across Home Assistant Core integrations, regenerates core requirement files, runs verification tests and prek lint, and prepares a pull request with proper release/compare links.
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
pause
Pause Mem0 memory capture on this machine. Use when the user wants to stop memories being recorded, for example for private work or experiments.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.