reprompter-team

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

A team-based workflow that divides a large task among two to five software agents, runs their work, and evaluates the result.

In plain words
What is it for?
It is for splitting complex work into independent areas, assigning each area to an agent, combining the results, and checking the final output.
Why use it?
It reduces the need to coordinate separate agents, prompts, runtimes, and retries by hand. It supports several ways of running agents, including sequential execution when needed.

Skill for Cursor

Written for Cursor: shipped in a Cursor plugin. Also seen: names the AskUserQuestion tool; positional $N argument; mentions Claude Code.

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`. Content below is verbatim from root SKILL.md lines 594-840 and 957-993. Phase 3 .

Part of the reprompter plugin — 5 skills shipped together

Good fit It is for splitting complex work into independent areas, assigning each area to an agent, combining the results, and checking the final output.

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-team

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-team

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/aytuncyildizli/reprompter/reprompter-team"><img src="https://agentmods.dev/badge/skills/aytuncyildizli/reprompter/reprompter-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 217 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,174 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.00217 $0.04174
Opus 5.5 $0.00087 $0.01670
Sonnet 5.5 $0.00043 $0.00835
Haiku 4.5 $0.00022 $0.00417

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

Security

Grade A, and why

reprompter-team 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-team/SKILL.md · 303 lines

How it starts

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

RePrompter — Team execution (Repromptverse)

Mode skill of the reprompter plugin. Entry/routing: ../reprompter/SKILL.md. Content below is verbatim from root SKILL.md lines 594-840 and 957-993. Phase 3 runtime detail (root lines 841-956 and 994-1283: runtime auto-pick, tool-schema guard, Options A-H) is in references/runtime-options.md; Settings (root 1832-1922) is in references/settings.md; Hermes Agent and Grok CLI support (root 2000-2071) is in references/hermes-grok-support.md. Templates (repromptverse, swarm, team-brief, *-swarm), outcome-schema.md and references/runtime/*.md are copied alongside. scripts/<name> paths resolve to the bundled ../reprompter/scripts/<name> (e.g. node ../reprompter/scripts/run-supervisor.js).

Required reading: ../reprompter/references/advanced-features.md (capability routing, layered context, artifact gate, flags, telemetry, Flywheel). The always-on rules in ../reprompter/SKILL.md → "Core shared rules" (context check, uncertainty permission, WHAT not HOW) apply to every per-agent prompt.

Team execution: Repromptverse (Agent Teams)

TL;DR

Raw task in → quality output out. Every agent gets a reprompted prompt.

Phase 1: Score raw prompt, dimension interview if needed, plan team, show Agent Cards (YOU do this, ~45s)
Phase 2: Write XML-structured prompt per agent (YOU do this, ~2min)
Phase 3: Launch agents (tmux, TeamCreate, Workflow tool, sessions_spawn, Codex, or sequential) (AUTOMATED)
Phase 4: Show Result Cards, score, retry if needed (YOU do this)

Key insight: The reprompt phase costs ZERO extra tokens — YOU write the prompts, not another AI.

Repromptverse control plane (Microsoft-inspired)

Every multi-agent run must include:

  1. Routing policy — who speaks next and why (selector-style routing for non-trivial teams)
  2. Termination policy — max turns, max wall time, and no-progress stop condition
  3. Artifact contract — one writer per output file, fixed schema for handoffs
  4. Evaluator loop — score each artifact, retry only with delta prompts (max 2 retries)

Read the full file on GitHub · 303 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 · 303 lines · 217 tokens per session scan A 823998f28aa8

Subscribe to this mod's changes

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

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens