agentmods.dev

discuss-change

discuss-change is a skill for Claude Code from tobihagemann/turbo. It costs 46 tokens per session (2,700 once invoked), scanned A, original, MIT.

A guided discussion workflow for deciding how a software change should work before implementation. It asks about unresolved product choices, agrees on the approach, and then starts implementation.

In plain words
What is it for?
Use it when you want to be interviewed about a change, settle its design, and then implement the agreed result.
Why use it?
It prevents code from being written around unstated requirements or unresolved choices such as optional versus required behavior. The discussion creates a shared understanding of the change.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the AskUserQuestion tool; mentions Codex.

Part of the turbo plugin — 71 skills shipped together

not rated 420repo +1 changed today A scan SkillSpector: warn 46 tokens original MIT

Good fit Use it when you want to be interviewed about a change, settle its design, and then implement the agreed result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tobihagemann/turbo/discuss-change
View source ↗ tobihagemann/turbo
Install

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.

Any agent
npx skills add tobihagemann/turbo --skill discuss-change
Clone the repo
git clone --depth 1 https://github.com/tobihagemann/turbo

Made for: Claude Code.

Or install turbo, the plugin that ships this one along with the rest of its 71 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 discuss-change

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/tobihagemann/turbo/discuss-change"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/discuss-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,700 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 12
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
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.00046 $0.02700
Opus 5.5 $0.00018 $0.01080
Sonnet 5.5 $0.00009 $0.00540
Haiku 4.5 $0.00005 $0.00270

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

Security

Grade A, and why

discuss-change 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 today.

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.

claude/skills/discuss-change/SKILL.md · 109 lines

How it starts

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

Discuss Change

Escalate open decisions, agree on the implementation shape, then implement.

Task Tracking

Use TaskCreate to create a task for each step:

  1. Capture the task
  2. Escalate product decisions
  3. Deep-dive discussion
  4. Confirm the shape
  5. Act on the user's reply
  6. Run /implement skill

Step 1: Capture the Task

Absorb the request without interrupting. Take the task from the user's request, or from conversation context when the task was already established. Restate the goal in one or two sentences and confirm.

Step 2: Escalate Product Decisions

Identify product or design decisions the request did not resolve. Escalate these via AskUserQuestion before any code is written. Read the code the change would touch before judging whether a bullet matches. Skip when no bullet below matches the change.

Escalate when:

  • The change requires choosing between user-facing behaviors the request did not specify (opt-in vs opt-out, strict vs lenient, sync vs async)
  • The change assumes product requirements that were not stated
  • Design trade-offs affect UX or product direction rather than technical implementation
  • Multiple valid approaches exist and the choice is a matter of product preference, not technical merit
  • The change would introduce a pattern not yet established in this codebase, or follow one sourced from outside it
  • The change adds consistency or durability machinery (a lease, lock, queue, versioning scheme, or new persistent entity) that no stated requirement demands; carrying that machinery is itself a product decision
  • A constraint on the solution that someone other than the user set and the user has not confirmed, such as a request relayed from another session or a consuming project's stated needs, rules out an option that is sounder on technical merit; offer that option and name the constraint it relaxes

Do not escalate technical decisions the agent can make autonomously: which data structure, which existing pattern to follow, internal implementation approach. The boundary is product intent.

Read the full file on GitHub · 109 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. today Changed · +1 lines a3a32b0f81f9
  2. 2d ago Changed 70c5199f258b
  3. 3d ago Changed · -42 tokens per session f759170d7806
  4. 20d ago Changed 205abac5fd31
  5. 1mo ago Changed · +1 lines 5e038babd399
  6. 1mo ago Changed · +4 lines 6828fef107d7
  7. 1mo ago Changed · +2 lines 520a31e3cb78
  8. 1mo ago Changed · +2 lines 6a1cd23f8a92
  9. 1mo ago Changed 2e2f9ba46326
  10. 1mo ago First seen · 99 lines · 88 tokens per session scan A 5e0e82cbca0a

Subscribe to this mod's changes

discuss-change is a skill published in the GitHub repository tobihagemann/turbo (420 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 2,700 once invoked, about $0.0002 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.

Claude CodePlanningagent-skillsclaude-skillscodexdeveloper-toolsskills
Related

discuss-change compared with skills from other repositories

discuss-change next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
discuss-changetobihagemann/turboSkill420todayMITA46Claude Code
offensive-c2-frameworksSnailSploit/Claude-RedSkill11kyesterdayMITA250Claude Code, Codex
offensive-crypto-attacksSnailSploit/Claude-RedSkill11kyesterdayMITA261Claude Code, Codex
offensive-parameter-pollutionSnailSploit/Claude-RedSkill11kyesterdayMITA0Claude Code, Codex
offensive-z-waveSnailSploit/Claude-RedSkill11kyesterdayMITA113Claude Code, Codex
fiscalisteromainsimon/paperasseSkill2.6ktodayMITA306Claude Code
comptableromainsimon/paperasseSkill2.6ktodayMITA248Claude Code