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 skills add JeremyDev87/codingbuddy --skill agent-discussion-panelgit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWrote 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/jeremydev87/codingbuddy/agent-discussion-panel)<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/agent-discussion-panel"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/agent-discussion-panel/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.
<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/agent-discussion-panel"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/agent-discussion-panel.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00050 | $0.04620 |
| Opus 5.5 | $0.00020 | $0.01848 |
| Sonnet 5.5 | $0.00010 | $0.00924 |
| Haiku 4.5 | $0.00005 | $0.00462 |
Grade A, and why
agent-discussion-panel 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 2mo 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 — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Discussion Panel (TUI)
Overview
The Agent Discussion Panel is a terminal UI component that renders multi-agent debates as a structured, scrollable panel. It consumes DiscussionResult data (from the AgentOpinion protocol) and renders it using the box-drawing format defined by the agent-discussion formatter skill.
Core principle: The panel is a layout container, not a formatter. It delegates all opinion rendering to the agent-discussion formatter and focuses on panel chrome, streaming lifecycle, and spatial arrangement.
Iron Law:
THE PANEL NEVER FORMATS OPINIONS — IT ARRANGES THEM
Formatting = agent-discussion skill. Layout = this skill.
Relationship to Other Components
┌─────────────────────────────────────────────────┐
│ AgentOpinion Protocol (discussion.types.ts) │
│ Defines: AgentOpinion, DiscussionResult │
└──────────────────┬──────────────────────────────┘
│ data
▼
┌─────────────────────────────────────────────────┐
│ agent-discussion (formatter skill) │
│ Renders: box chars, severity badges, consensus │
└──────────────────┬──────────────────────────────┘
│ formatted blocks
▼
┌─────────────────────────────────────────────────┐
│ agent-discussion-panel (THIS skill — TUI layout) │
│ Arranges: header, stream, consensus, summary │
└─────────────────────────────────────────────────┘
When to Use
- Building a TUI that displays multi-agent discussion output
- Implementing a codingbuddy terminal dashboard with agent debate panels
- Rendering streaming agent opinions in real time within a bounded panel region
- Displaying EVAL mode consolidated output in a structured panel
When NOT to Use
- Formatting individual agent opinions (use
agent-discussionformatter) - Building web/HTML UIs (this is terminal-only)
- Rendering a single agent's output (no panel needed)
- Logging or piping output to files (panel chrome adds noise)
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.
- 2mo ago First seen · 449 lines · 50 tokens per session scan A bd28c35cd044
agent-discussion-panel is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 7mo ago), licensed MIT. It adds 50 tokens to every session and 4,620 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.
agent-discussion-panel compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| agent-discussion-panelJeremyDev87/codingbuddy | Skill | 31 | 7mo ago | MIT | A | 50 | Claude Code |
| ring:migrating-to-lib-observabilityLerianStudio/ring | Skill | 218 | 11d ago | Apache-2.0 | A | 104 | Cursor |
| ring:exploring-codebasesLerianStudio/ring | Skill | 218 | 11d ago | Apache-2.0 | A | 91 | Cursor |
| ring:searching-codeLerianStudio/ring | Skill | 218 | 11d ago | Apache-2.0 | A | 74 | Claude Code, Cursor |
| ring:instrumenting-streaming-eventsLerianStudio/ring | Skill | 218 | 11d ago | Apache-2.0 | A | 102 | Cursor |
| ring:planning-codebase-simplificationLerianStudio/ring | Skill | 218 | 11d ago | Apache-2.0 | A | 105 | Cursor |
| ring:mapping-feature-relationshipsLerianStudio/ring | Skill | 218 | 11d ago | Apache-2.0 | A | 104 | Cursor |