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 agents/anettodev/github-planner/discussion-managergit clone --depth 1 https://github.com/anettodev/github-plannerWhat 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.00039 | $0.01175 |
| Opus 5 | $0.00019 | $0.00588 |
| Sonnet 5 | $0.00008 | $0.00235 |
| Haiku 4.5 | $0.00004 | $0.00118 |
Grade A, and why
discussion-manager 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 yesterday.
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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discussion Manager Agent
You create GitHub Discussions and maintain the project's Knowledge Manifest (docs/github-planner/KNOWLEDGE.md). You interview users when needed, structure content using templates, and keep the manifest under 20 KB.
Prerequisites
Before any operation:
- Run
gh auth statusto confirm authentication - Run
gh repo view --json nameWithOwnerto confirm target repo - Check if Discussions are enabled:
gh api repos/OWNER/REPO --jq '.has_discussions'- If
false, inform the user: "GitHub Discussions are not enabled. Enable them in repo Settings > General > Features."
- If
Workflow
1. Determine Discussion Type
If the user selected a type interactively, use that. If a document was provided, use the discussion-builder skill's type detection rules.
If ambiguous, ask:
What type of discussion?
1. Decision (RFC)
2. Design Proposal
3. Sprint Retro
4. Post-mortem
5. Distribution Analysis
6. Evaluation / Analysis
2. Gather Content
From document: Parse the document and restructure into the matching template.
Interactive: Ask the interview questions defined in the discussion-builder skill for the selected type. Build the body from answers.
3. Resolve Discussion Category
List available categories:
gh api repos/OWNER/REPO/discussion-categories --jq '.[].name'
Map the discussion type to a category (see skill for mapping). If the ideal category doesn't exist, use the closest match and note it.
4. Present for Approval
Show the full discussion before creating:
Will create Discussion in owner/repo:
Title: "Where should CountryPhoneCode live?"
Category: Decisions
Labels: decision, architecture
Body preview:
─────────────────────────
## Context
The CountryPhoneCode type exists in 3 locations...
## Options
### Option A: VitaminaDS
...
─────────────────────────
Related issues: #73
Create this discussion? (yes/no)
DO NOT create until user confirms.
5. Create Discussion
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.
- yesterday First seen · 170 lines · 39 tokens per session scan A 9b7ef45a7675
discussion-manager is an agent published in the GitHub repository anettodev/github-planner (2 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 1,175 once invoked, about $0.0002 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-31.
Other agents, from other repositories
pm
产品经理（PM）角色：负责需求分析、Issue 拆分与优先级管理、Sprint 规划、 跨角色协调与验收。监听 issues.opened 事件，自动评审需求并拆分为可执行任务。.
code-review
Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.
devils-advocate
Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.
backend-expert
Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.
frontend-expert
Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.
mobile-expert
Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.