Borrowing it
Nothing to install: this file belongs to FunnelEnvy/marketing-clis. 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/FunnelEnvy/marketing-clis/master/.claude/skills/generate-cli/SKILL.mdgit clone --depth 1 https://github.com/FunnelEnvy/marketing-clisWrote 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/funnelenvy/marketing-clis/generate-cli)<a href="https://agentmods.dev/skills/funnelenvy/marketing-clis/generate-cli"><img src="https://agentmods.dev/badge/skills/funnelenvy/marketing-clis/generate-cli.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.00026 | $0.01058 |
| Opus 5 | $0.00013 | $0.00529 |
| Sonnet 5 | $0.00005 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
generate-cli 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 7d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a Marketing CLI
Generate a complete CLI tool for a marketing platform from its API documentation.
Usage
/generate-cli <tool-name> <api-docs-url>
Examples:
/generate-cli hubspot https://developers.hubspot.com/docs/api/overview
/generate-cli sendgrid https://docs.sendgrid.com/api-reference
Arguments
The user must provide:
- tool-name — lowercase name for the CLI (e.g.,
hubspot,sendgrid). Becomes the binary name, repo name ({tool}-cli), and npm package (@funnelenvy/{tool}-cli). - api-docs-url — URL to the platform's REST API documentation.
If either is missing, ask for it before proceeding.
Workflow
Follow all four phases in order. Read CLAUDE.md at the repo root for the full standards — it is the source of truth for naming, auth patterns, output formatting, error handling, and file structure.
Phase 1: API Discovery
- Fetch and read the API docs at the provided URL
- Check for an OpenAPI/Swagger spec (
/openapi.json,/swagger.json) - If a spec exists, save it as
api-spec.jsonin the CLI repo - Build an endpoint inventory:
- Group endpoints by resource (campaigns, contacts, reports, etc.)
- Note the auth method (API key, OAuth2, both)
- Note rate limits and pagination patterns
- Note response envelope format
- Save the inventory as
api-inventory.mdin the CLI repo
Reference: prompts/api-discovery.md
Phase 2: CLI Design
- Map API resources to command groups (nouns):
campaigns,lists,reports - Map CRUD operations to subcommands (verbs):
list,get,create,update,delete - Design the auth flow:
--api-keyflag > env var > config file > interactive login - Plan output: JSON (default), table, CSV for all data commands
- Write the command tree and present it to the user before writing code
- Prioritize the most-used endpoints — don't try to cover every endpoint
Reference: prompts/cli-design.md, generator/prompts/auth-patterns.md
Phase 3: Scaffold & Implement
What ships with it
21 files 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.
- prompts/api-discovery.md 1.5 KB
- prompts/auth-patterns.md 1.7 KB
- prompts/cli-design.md 2.0 KB
- prompts/testing.md 1.8 KB
- templates/node-cli/.github/workflows/ci.yml 723 B
- templates/node-cli/.github/workflows/release.yml 840 B
- templates/node-cli/.gitignore 57 B
- templates/node-cli/AGENTS.md 1.0 KB
- templates/node-cli/CLAUDE.md 130 B
- templates/node-cli/LICENSE 1.0 KB
- templates/node-cli/package.json 995 B
- templates/node-cli/README.md 1.6 KB
- templates/node-cli/src/auth.ts 1.0 KB runs code
- templates/node-cli/src/commands/.gitkeep 0 B
- templates/node-cli/src/index.ts 336 B runs code
- templates/node-cli/src/lib/config.ts 1.2 KB runs code
- templates/node-cli/src/lib/http.ts 2.3 KB runs code
- templates/node-cli/src/lib/output.ts 1.7 KB runs code
- templates/node-cli/tsconfig.json 439 B
- templates/node-cli/tsup.config.ts 213 B runs code
- templates/node-cli/vitest.config.ts 140 B runs code
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.
- 7d ago First seen · 98 lines · 26 tokens per session scan A 2a276e118393
generate-cli is a skill published in the GitHub repository FunnelEnvy/marketing-clis (11 stars, last pushed 6mo ago), licensed MIT. It adds 26 tokens to every session and 1,058 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…