thoth:extension

A command for creating and managing project-specific extensions and experiment records for a dashboard or TUI, meaning a text-based interface in a terminal. It can also list and validate those items.

In plain words
What is it for?
Use it to create, list, validate, and manage dashboard or terminal-interface extensions and entries in the experiment registry.
Why use it?
It avoids handling these project objects manually and provides checks before they are used.

Command

Install

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.

agentmods
npx agentmods add commands/seeleai/thoth/extension
Clone the repo
git clone --depth 1 https://github.com/SeeleAI/Thoth
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 594 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00594
Opus 5 $0.00012 $0.00297
Sonnet 5 $0.00005 $0.00119
Haiku 4.5 $0.00002 $0.00059

Measured 2d ago against content hash 517e6735de72, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

thoth:extension 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.

commands/extension.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/thoth:extension

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_EXTENSION_ARGUMENTS_FILE="$(mktemp -t thoth-extension-arguments.XXXXXX)"
trap 'rm -f "$THOTH_EXTENSION_ARGUMENTS_FILE"' EXIT
cat > "$THOTH_EXTENSION_ARGUMENTS_FILE" <<'THOTH_EXTENSION_ARGUMENTS_EOF'
$ARGUMENTS
THOTH_EXTENSION_ARGUMENTS_EOF
"${CLAUDE_PLUGIN_ROOT}/scripts/thoth-claude-command.sh" extension --thoth-arguments-file "$THOTH_EXTENSION_ARGUMENTS_FILE"

Response Contract

  • Treat the structured bridge payload above as the only authority for this invocation.
  • If bridge_success is false, report the exact bridge failure and stop.
  • If stdout starts with version=, repeat stdout exactly and output nothing else.
  • If bridge_success is true, report only the real command result in one short receipt.
  • If extra evidence is required, inspect only the smallest artifact explicitly named by the bridge payload.
  • Do not launch broad Explore, Task, cache/source scans, or background investigation after the bridge result.
  • If the result exposes blockers or asks for human decisions, use AskUserQuestion to ask only the unresolved questions and stop.
  • Do not expand into runtime explanation, walkthroughs, or extra command execution.

Authority Summary

Route

  • route_class: mechanical_fast
  • intelligence_tier: none
  • packet_authority_mode: result_envelope

Objective

Create, list, validate, and manage project-local Dashboard/TUI extensions and experiment registry objects while preserving manifest schema v3 and local audit receipts.

Hard Stops

  1. Do not execute extension Python code while creating, listing, validating, or managing experiments.
  2. Do not write extension sources outside .thoth/extensions/plugins unless an explicit project-relative source was provided.
  3. Do not treat local action receipts as portable project authority.
  4. Do not persist absolute downstream paths into portable experiment registry objects.
  5. Do not invent extension capabilities beyond the CLI arguments and manifest contents.

Read the full file on GitHub · 64 lines

Changes

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.

  1. 2d ago First seen · 64 lines · 24 tokens per session scan A 517e6735de72

Subscribe to this mod's changes

thoth:extension is a command published in the GitHub repository SeeleAI/Thoth (51 stars, last pushed 23d ago), licensed MIT. It adds 24 tokens to every session and 594 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.