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/roboco-io/ghx-cli/discussiongit clone --depth 1 https://github.com/roboco-io/ghx-cliWhat 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.01707 |
| Opus 5 | $0.00000 | $0.00853 |
| Sonnet 5 | $0.00000 | $0.00341 |
| Haiku 4.5 | $0.00000 | $0.00171 |
Grade A, and why
discussion 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ghx discussion
Manage GitHub Discussions in repositories.
Synopsis
ghx discussion <command> [arguments] [flags]
Aliases
ghx discussionghx discghx discussions
Description
The discussion command group provides comprehensive discussion management for GitHub Discussions, including creating, viewing, commenting, and managing discussion state.
Commands
| Command | Description |
|---|---|
list |
List discussions |
view |
View discussion details |
create |
Create a new discussion |
edit |
Edit a discussion |
delete |
Delete a discussion |
close |
Close a discussion |
reopen |
Reopen a discussion |
lock |
Lock a discussion |
unlock |
Unlock a discussion |
comment |
Add a comment |
answer |
Mark/unmark as answer |
category |
Manage categories |
ghx discussion list
List discussions in a repository.
ghx discussion list <owner/repo> [flags]
Flags
| Flag | Description | Default |
|---|---|---|
--category |
Filter by category slug | - |
--state |
Filter by state (open, closed, all) | all |
--answered |
Show only answered | false |
--unanswered |
Show only unanswered | false |
-L, --limit |
Maximum number of discussions | 20 |
--format |
Output format (table, json) | table |
Examples
# List all discussions
ghx discussion list myorg/repo
# List open discussions
ghx discussion list myorg/repo --state open
# Filter by category
ghx discussion list myorg/repo --category ideas
# Show unanswered Q&A
ghx discussion list myorg/repo --category q-a --unanswered
# JSON output
ghx discussion list myorg/repo --format json
ghx discussion view
View a discussion.
ghx discussion view <owner/repo> <number> [flags]
Flags
| Flag | Description | Default |
|---|---|---|
--comments |
Include comments | false |
--format |
Output format (table, json) | table |
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 · 352 lines · 0 tokens per session scan A b7e737a35b0a
discussion is a command published in the GitHub repository roboco-io/ghx-cli (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,707 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-31.
Other commands, from other repositories
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.