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 commands/agentsea/flashbacker/discussgit clone --depth 1 https://github.com/agentsea/flashbackerWhat 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.00000 | $0.00816 |
| Opus 5 | $0.00000 | $0.00408 |
| Sonnet 5 | $0.00000 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00082 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Discussion
Multi-agent discussion coordination using main conversation orchestration.
Usage
/fb:discuss <agent1>,<agent2>,<agent3> <topic>
Launch coordinated discussions between specialized Claude Code agents with automatic orchestration and synthesis.
Available Agents
Use flashback agent --list to see current available agents and descriptions
Important: If any agent requested by the user does not exist, return "❌ Agent '{agent_name}' does not exist" and then run flashback agent --list to show available agents. Do NOT proceed with the discussion if any requested agent is missing.
ELSE (if all requested agents exist), proceed with the rest of this command.
Examples
/fb:discuss architect,security "API authentication strategy"/fb:discuss frontend,performance "React rendering optimization"/fb:discuss architect,backend,devops "Microservices deployment strategy"/fb:discuss security,qa "Penetration testing approach"
How It Works
- Parse Arguments: Extract agent list and discussion topic from command
- Gather Context: Run
flashback agent --contextto get project context bundle - PARALLEL Agent Calls: Call ALL requested agents simultaneously in one message using multiple tool calls
- Collect Responses: Gather all agent responses in main conversation
- Synthesize Results: Analyze responses for consensus, disagreements, and recommendations
- User Confirmation: Present findings and ask for approval before taking actions
I'll coordinate this multi-agent discussion by calling each agent individually and synthesizing their responses.
Arguments: "$ARGUMENTS"
AGENT VALIDATION (CRITICAL - DO THIS FIRST):
First, let me check which agents are available and validate the requested agents.
- Get Available Agents: Run
flashback agent --listto see all current available agents - Parse Requested Agents: Extract comma-separated agent names from the first part of arguments (before first space)
- Validate Each Agent: Check if each requested agent exists in the available agents list
- If ANY agent is missing:
- Display: "❌ Agent '{agent_name}' does not exist"
- Show the complete list of available agents from
flashback agent --list - STOP HERE - DO NOT PROCEED with the discussion
- If ALL agents exist: Continue with the rest of the discussion process below
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.
- 2d ago First seen · 73 lines · 0 tokens per session scan A bfd8a566eb99
discuss is a command published in the GitHub repository agentsea/flashbacker (57 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 816 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.