discuss

discuss is a skill for Claude Code, Codex from asysta-act/agent-flow. It costs 17 tokens per session (465 once invoked), scanned A, original, MIT.

A discussion tool that asks two or three coding agents for separate views on a topic and combines their responses. You can choose the participating agents or use the default group.

In plain words
What is it for?
Reviewing a design, bug, or implementation question with selected agents such as a reviewer, fixer, or architect.
Why use it?
It brings multiple technical perspectives into one conversation instead of requiring separate discussions. This can expose different concerns before a decision is made.

Skill for Claude CodeCodex

Part of the agent-flow plugin — 17 skills, 17 agents shipped together

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.

agentmods
npx agentmods add skills/asysta-act/agent-flow/discuss
Any agent
npx skills add asysta-act/agent-flow --skill discuss
Clone the repo
git clone --depth 1 https://github.com/asysta-act/agent-flow

Made for: Claude Code, Codex.

Or install agent-flow, the plugin that ships this one along with the rest of its 17 skills, 17 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/asysta-act/agent-flow/discuss.svg)](https://agentmods.dev/skills/asysta-act/agent-flow/discuss)
Your own site
<a href="https://agentmods.dev/skills/asysta-act/agent-flow/discuss"><img src="https://agentmods.dev/badge/skills/asysta-act/agent-flow/discuss.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 465 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00017 $0.00465
Opus 5 $0.00009 $0.00233
Sonnet 5 $0.00003 $0.00093
Haiku 4.5 $0.00002 $0.00047

Measured 4d ago against content hash de8596529052, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

discuss 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 4d 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.

skills/discuss/SKILL.md · 61 lines

What it actually says

Discuss

Input: $ARGUMENTS = topic or question + optional --agents <list> (comma-separated agent names)

Steps

  1. Parse $ARGUMENTS:

    • --agents reviewer,fixer,architect → agent_list
    • Default agent_list: reviewer,fixer,architect (if not specified)
    • Remainder = topic
    • Max 3 agents per discussion
  2. For each agent in agent_list (in parallel): Before dispatch, check Agent Overrides: for each agent you dispatch, follow ../../core/agent-override-injector.md for that agent's overrides. Run agent via Task tool with context:

    You are participating in a multi-agent discussion about: {topic}
    Your role: {agent description from frontmatter}
    Style: {agent style from frontmatter}
    
    Provide your perspective on this topic in 100-200 words.
    Focus on concerns and insights specific to YOUR expertise.
    Be opinionated — disagree with conventional wisdom if your expertise suggests otherwise.
    
  3. Collect all agent responses.

  4. Display as structured discussion:

    ## Discussion: {topic}
    
    ### {agent-1 name} ({agent-1 style})
    {agent-1 perspective}
    
    ### {agent-2 name} ({agent-2 style})
    {agent-2 perspective}
    
    ### {agent-3 name} ({agent-3 style})
    {agent-3 perspective}
    
    ### Synthesis
    {synthesize key agreements, disagreements, and recommended approach}
    
  5. Ask: "Follow up on any perspective? [agent name / done]" If user picks an agent → run that agent again with the full discussion context for deeper exploration.

Rules

  • Max 3 agents per discussion
  • Read-only — no code changes
  • Each agent response: 100-200 words max
  • Discussion is for exploration, not decisions — no pipeline side effects
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. 4d ago First seen · 61 lines · 17 tokens per session scan A de8596529052

Subscribe to this mod's changes

discuss is a skill published in the GitHub repository asysta-act/agent-flow (12 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 465 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.

Related

Other skills, from other repositories

html-ppt-zhangzara-broadside

OpenDesign's product-launch announcement and press narrative — the headline, the proof points, and the call to action. Built as a decision-grade marketing & GTM deck for press, community, prospects.

nexu-io/open-design · 52 tokens

geo-prospect

CRM-lite for managing GEO agency prospects and clients. Track leads through the full sales pipeline: Lead → Qualified → Proposal Sent → Won → Lost. Store audit history, notes, deal values, and generate pipeline summaries. Use when user says "prospect", "lead", "client", "pipeline", "crm", "nuovo prospect", "aggiungi…

zubair-trabzada/geo-seo-claude · 87 tokens

drug-design

End-to-end drug discovery pipeline orchestration. Deterministic Python script that auto-chains structure prediction, pocket detection, de novo design, docking, scoring, and ADMET filtering into reproducible workflows.

synthetic-sciences/openscience · 44 tokens

workflow-creation

Create a new Stencila workflow. Use when asked to create, write, scaffold, or set up a workflow directory or WORKFLOW.md file. Covers workflow discovery, duplicate-name checks, ephemeral workflows, WORKFLOW.md frontmatter, DOT pipeline authoring, goals, agents, branching, composition, and validation.

stencila/stencila · 67 tokens

bump-mthds

Move this repo's exact mthds dependency pin to the latest release on PyPI (or a version you name), re-lock, adapt the engine source to whatever the new release broke, run the checks, and write the CHANGELOG entry — stopping before the commit. Use whenever the user says "bump mthds", "update mthds", "upgrade mthds"…

Pipelex/pipelex · 286 tokens

add-migration

Write a migration ledger entry for a configuration schema change in pipelex, so that a user's existing file can be repaired instead of thrown away. Use when make check-migration-schemas (alias cmig) or make check-ledger (alias cl) refuses a change, when the user says "add a migration", "write the ledger entry", "the…

Pipelex/pipelex · 154 tokens