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/seeleai/thoth/discussgit clone --depth 1 https://github.com/SeeleAI/ThothWhat 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.00016 | $0.00839 |
| Opus 5 | $0.00008 | $0.00419 |
| Sonnet 5 | $0.00003 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
thoth: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.
/thoth:discuss
Generated Surface
This file is generated from thoth.command_specs.COMMAND_SPECS. Do not hand edit.
Real Runtime Execution
The repo-local Thoth runtime command for this slash command has already been executed before Claude sees this prompt.
THOTH_DISCUSS_ARGUMENTS_FILE="$(mktemp -t thoth-discuss-arguments.XXXXXX)"
trap 'rm -f "$THOTH_DISCUSS_ARGUMENTS_FILE"' EXIT
cat > "$THOTH_DISCUSS_ARGUMENTS_FILE" <<'THOTH_DISCUSS_ARGUMENTS_EOF'
$ARGUMENTS
THOTH_DISCUSS_ARGUMENTS_EOF
"${CLAUDE_PLUGIN_ROOT}/scripts/thoth-claude-command.sh" discuss --thoth-arguments-file "$THOTH_DISCUSS_ARGUMENTS_FILE"
Response Contract
- Treat the structured bridge payload above as the only authority for this command invocation.
- If
bridge_successisfalse, report the exact bridge failure and stop. - If
runorloopis missing--work-id, show returned candidates and stop; do not invent, create, compile, or guess a work item. - If
bridge_successistrueand runtime events are present, summarize progress, terminal status, and risk from those events only. - Do not hand-edit
.thothor manually call runtime protocol commands; the Thoth RuntimeDriver advances phases. - If
packet.dispatch_modeisexternal_worker, do not duplicate the work locally; report the run id, worker mode, and the correct follow-up only. - If you only describe what should happen next instead of reporting the executed runtime result, treat that as failure.
- Use AskUserQuestion until compact authority categories are explicit: goal, constraints, decisions, risks, approach_notes, and open_questions.
- On major semantic changes, write a draft authority checkpoint through
packet.protocol_commands.checkpoint_authority. - When no material assumptions remain, close with the compact authority categories plus
packet.work_json_templateorpacket.work_graph_schemathroughpacket.protocol_commands.close_authority. - Use
packet.init_project_patch_schemaonly for init discussions; ordinary discussions cannot patch project name, description, or directions. - When closing authority for an existing work item, preserve its stable work_id; do not omit work_id and create a timestamp work item.
- Do not create ready work if any open_questions remain in the authority capsule.
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 · 16 tokens per session scan A df402b16281e
thoth:discuss is a command published in the GitHub repository SeeleAI/Thoth (51 stars, last pushed 23d ago), licensed MIT. It adds 16 tokens to every session and 839 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 commands, from other repositories
build
Bulk-build ArcKit artefacts in parallel via subagent-orchestrated waves with resumable state.
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
autobot-stop
Stop an autobot session (kill tmux and dev environment, but keep the worktree).
autobot-result
Print the most recent result.md for an autobot session, so the user can see how a bot is doing without attaching to its tmux session.
ci-report
Generate a CI failure report for PR $PRNUMORURL (or current branch if no argument given).
autobot-list
List all autobot sessions with status information.