reprompter-improve

reprompter-improve is a skill for Cursor from AytuncYildizli/reprompter. It costs 154 tokens per session (4,425 once invoked), scanned A, original, MIT.

A prompt-improvement guide that turns a rough request into a structured specification or, for a whole product, an outcome-focused build brief. It also supports preparing the result for commands, workflows, or agent teams.

In plain words
What is it for?
It is for improving prompts, deciding whether a request needs a detailed specification or product brief, and preparing the improved prompt for /goal, workflow, or multi-agent use.
Why use it?
Vague prompts leave important requirements and uncertainties unstated. This guide helps decide the right output shape and make the requested result clearer before another model acts on it.

Skill for Cursor

Written for Cursor: shipped in a Cursor plugin. Also seen: names the AskUserQuestion tool; mentions Codex; built for openclaw.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is Mode skill of the `reprompter` plugin. Entry/routing: `../reprompter/SKILL.md`. Output formats beyond paste (`/goal` card, `.workflow.js`, headless-relay delive.

Part of the reprompter plugin — 5 skills shipped together

Good fit It is for improving prompts, deciding whether a request needs a detailed specification or product brief, and preparing the improved prompt for /goal, workflow, or multi-agent use.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/AytuncYildizli/reprompter
agentmods
npx agentmods add skills/aytuncyildizli/reprompter/reprompter-improve

Made for: Cursor.

Or install reprompter, the plugin that ships this one along with the rest of its 5 skills.

Wrote 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.

agentmods badge for reprompter-improve

README.md
[![agentmods](https://agentmods.dev/badge/skills/aytuncyildizli/reprompter/reprompter-improve/github.svg)](https://agentmods.dev/skills/aytuncyildizli/reprompter/reprompter-improve)
Your own site
<a href="https://agentmods.dev/skills/aytuncyildizli/reprompter/reprompter-improve"><img src="https://agentmods.dev/badge/skills/aytuncyildizli/reprompter/reprompter-improve/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.

agentmods 80×15 button for reprompter-improve

Your own site · 80×15
<a href="https://agentmods.dev/skills/aytuncyildizli/reprompter/reprompter-improve"><img src="https://agentmods.dev/badge/skills/aytuncyildizli/reprompter/reprompter-improve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 154 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,425 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00154 $0.04425
Opus 5.5 $0.00062 $0.01770
Sonnet 5.5 $0.00031 $0.00885
Haiku 4.5 $0.00015 $0.00443

Measured yesterday against content hash c88b98aa6c56, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

reprompter-improve 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 yesterday.

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.

grokbot-plugin/skills/reprompter-improve/SKILL.md · 277 lines

How it starts

The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.

RePrompter — Improve (Single prompt)

Mode skill of the reprompter plugin. Entry/routing: ../reprompter/SKILL.md. Output formats beyond paste (/goal card, .workflow.js, headless-relay delivery): ../reprompter-goal-workflow/SKILL.md. Whole-product builds: ../reprompter-oneshot/SKILL.md. Multi-agent: ../reprompter-team/SKILL.md. scripts/<name> paths resolve to the bundled ../reprompter/scripts/<name> (e.g. ../reprompter/scripts/outcome-record.js).

Required reading: ../reprompter/references/advanced-features.md (context engineering, uncertainty handling, token budget, Flywheel, pattern library). The always-on rules in ../reprompter/SKILL.md → "Core shared rules" (context check, uncertainty permission, WHAT not HOW) apply to every generated prompt. Every template named below lives in references/ next to this file. Content below is verbatim from root SKILL.md (lines 358-591, 1560-1606) except where marked Moved.

Intent: Improve (Single prompt)

Shape decision (specifiability router)

Before the template pick, decide the OUTPUT SHAPE from the interview:

Default is spec-XML. Only switch to outcome-prose on a STRONG whole-product signal, and when in doubt, stay spec-XML — a scored structured prompt is never the wrong answer for a coding task, and it is what "reprompt this" has always produced.

  • Spec-XML (default) — any bounded change (bugfix, endpoint, refactor, a feature in named files), anything with an enumerable done-state, and anything ambiguous. Scored on the six dimensions, exactly as always.
  • Outcome-prose (only on a strong signal) — the ask is to build a WHOLE product or artifact from near-zero (a whole app/game/site/deck), OR it names a real product as the quality bar for a from-scratch build ("build me X like Linear"). Then emit the One-Shot three-paragraph shape (references/oneshot-template.md), including its constraints sentence for load-bearing negatives ("never touch auth"). Announce and offer the exit: "This looks like a whole-product build — I'll write an autonomous build prompt; say 'spec' for the structured, scored version instead." The user's override always wins. Outcome-prose is not scored on the six dimensions. This is the same artifact the Build intent produces — an Improve ask that is really a whole-product build and the Build intent converge on one prose brief, deliberately; there is no separate Improve-only build shape to disambiguate.
  • Mixed asks (a bounded change described with a reference, e.g. "add a settings page like Linear's to our app") are spec-XML: the reference informs the requirements, it does not trigger a from-scratch build. When genuinely unsure which one an ask is, ask one discriminator question — "a fresh build, or a change to something that exists?" — and default to spec-XML on a fresh session with no answer.

Read the full file on GitHub · 277 lines

Changes

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.

  1. yesterday First seen · 277 lines · 154 tokens per session scan A c88b98aa6c56

Subscribe to this mod's changes

reprompter-improve is a skill published in the GitHub repository AytuncYildizli/reprompter (118 stars, last pushed yesterday), licensed MIT. It adds 154 tokens to every session and 4,425 once invoked, about $0.0006 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-10-16.

Related

Other skills, from other repositories

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

agentmail

Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.

paperclipai/paperclip · 30 tokens

rowboat-spaces

How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.

rowboatlabs/rowboat · 60 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens