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 agentmods add skills/asysta-act/agent-flow/discussnpx skills add asysta-act/agent-flow --skill discussgit clone --depth 1 https://github.com/asysta-act/agent-flowWrote 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/asysta-act/agent-flow/discuss)<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>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 | $0.00017 | $0.00465 |
| Opus 5 | $0.00009 | $0.00233 |
| Sonnet 5 | $0.00003 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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.
What it actually says
Discuss
Input: $ARGUMENTS = topic or question + optional --agents <list> (comma-separated agent names)
Steps
-
Parse
$ARGUMENTS:--agents reviewer,fixer,architect→ agent_list- Default agent_list:
reviewer,fixer,architect(if not specified) - Remainder = topic
- Max 3 agents per discussion
-
For each agent in agent_list (in parallel): Before dispatch, check Agent Overrides: for each agent you dispatch, follow
../../core/agent-override-injector.mdfor 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. -
Collect all agent responses.
-
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} -
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
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.
- 4d ago First seen · 61 lines · 17 tokens per session scan A de8596529052
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.
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.
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…
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.
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.
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"…
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…