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 freema/cursor-plugin-cc --skill composer-promptinggit clone --depth 1 https://github.com/freema/cursor-plugin-ccWrote 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/freema/cursor-plugin-cc/composer-prompting)<a href="https://agentmods.dev/skills/freema/cursor-plugin-cc/composer-prompting"><img src="https://agentmods.dev/badge/skills/freema/cursor-plugin-cc/composer-prompting/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/freema/cursor-plugin-cc/composer-prompting"><img src="https://agentmods.dev/badge/skills/freema/cursor-plugin-cc/composer-prompting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00575 |
| Opus 5.5 | $0.00012 | $0.00230 |
| Sonnet 5.5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
composer-prompting 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Composer Prompting
Use this skill when the cursor-runner subagent (or the main Claude thread) needs to turn a well-specified coding task into a prompt for the Cursor CLI (cursor-agent, Composer by default).
Cursor has no conversation context — whatever the target repo expects, you must bake into the prompt you send. Prompt Composer like a fast executor with a precise contract, not a collaborator you can clarify with mid-run. State the goal, the exact end state, the files it may touch, and how "done" is verified.
Ground the prompt in the target repo first
Before writing the prompt, use Read (only) to check the target repo for:
AGENTS.md,CLAUDE.md,.cursor/rules/**,.github/copilot-instructions.md,CONTRIBUTING.md— convention files.package.json/Taskfile.yml/Makefile/justfile— to learn which commands build and test the project.README.md— for the overall project goal (one sentence is enough).
Language and style follow the target repo, not this plugin. If the repo's commits, comments, or UI strings are in Czech / German / any other language, Composer must match — do not force English. If the repo is mixed (code in English, user copy in Czech), say so explicitly. When in doubt, tell Cursor: "match the existing style of surrounding files."
References — read the one you need
- references/prompt-anatomy.md — the five mandatory prompt sections + guardrails block, with a full worked example. Read before composing any delegate prompt.
- references/model-selection.md — the model escalation ladder, chunking heuristics for oversized plans, and resume-vs-fresh routing.
- references/composer-antipatterns.md — prompt shapes that reliably produce bad Composer runs, each with the fix. Skim when a previous run went sideways.
Assembly checklist
- Ground the prompt in the target repo's conventions and verify commands.
- Write the five sections plus the guardrails block, in order (see prompt-anatomy).
- Chunk anything bigger than one reviewable slice (see model-selection).
- Pick the smallest model that fits; default to
composer-2.5-fast. - Decide resume vs fresh.
- Remove redundant instructions before sending.
What ships with it
3 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.
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 · 37 lines · 31 tokens per session scan A 53df418d5b14
composer-prompting is a skill published in the GitHub repository freema/cursor-plugin-cc (36 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 575 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-30.
Other skills, from other repositories
ai-evaluation-engineering
An AI evaluation engineering specialist for testing models and prompts. The description does not provide enough detail to state which concrete operations it performs.
prompt-pilot
Rewrite a rough, vague prompt into a precise, context-enriched prompt. Explores the codebase read-only and weaves real file paths and symbols into the rewritten prompt — never implements the task itself. Use when the user asks to optimize, enrich, or improve a prompt before running it.
kanso-prompting
Use when rewriting, sharpening, or producing a prompt for Claude or another current frontier model. Sets standing rules for getting better LLM output through better prompts. Loaded by /kanso-task; not directly invoked by the user.
cursor-prompting
Prompt shaping rules for delegated cursor-agent tasks.
skill-meta-prompt
Craft better prompts using proven optimization techniques — use when your prompt needs refinement.
ai-workflow-architect
Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong. Use this to automate part of an operation, design an agent or MCP workflow, reduce repetitive manual work, connect tools into a…