docs

A documentation-only command for updating Untether's changelog, FAQ, project instructions, and reference pages when no code change is being delivered.

In plain words
What is it for?
Use it to reconcile standalone documentation changes, update frequently asked questions, or correct project guidance outside a feature or fix.
Why use it?
It provides a controlled way to fix documentation that has drifted without creating a code pull request. Code-related documentation work is routed into the normal delivery process instead.

Command for Claude Code

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/littlebearapps/untether/docs
Clone the repo
git clone --depth 1 https://github.com/littlebearapps/untether

Made for: Claude Code.

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,110 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.00027 $0.01110
Opus 5 $0.00014 $0.00555
Sonnet 5 $0.00005 $0.00222
Haiku 4.5 $0.00003 $0.00111

Measured yesterday against content hash c77fa2995431, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docs 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.

.claude/commands/docs.md · 84 lines

How it starts

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

You are handling /docs. /docs reconciles Untether's small doc surface outside a PR. It is an escape hatch, not the default path — docs completion is normally folded into /pr-dev (CHANGELOG + FAQ + `CLAUDE.md

Testsas a completion criterion). Reach for/docs` only when documentation

has drifted on its own and there is no code change to deliver alongside it.

User input: $ARGUMENTS

Untether adaptations (read first)

Load .claude/rules/workflow-commands.md (routing + cross-cutting rules), .claude/rules/help-faq.md, and .claude/rules/context-quality.md. Key points:

  • Authority: docs only. Edit CHANGELOG / docs/faq/faq.md / CLAUDE.md / docs/reference/*. Never code, never a PR (if a code branch is involved → route to /pr-dev, which folds docs in), never master/tag/release.
  • If a code change is in flight → STOP and route to /pr-dev. Do not split docs for a code change into a separate PR — that fragments delivery.
  • FAQ is gate-protected. docs/faq/faq.md accepts Edit/Write/append but blocks rm/mv/> (the help-faq-protect.sh hook). Never delete/move it.
  • Confirm-gated + idempotent. Surface the drafted edits and wait for a tap; re-running must not duplicate a CHANGELOG entry or FAQ Q/A.

When to use (vs /pr-dev)

Situation Command
Delivering code + its docs /pr-dev (docs folded in)
A doc drifted with no code change (stale FAQ, missing CHANGELOG link, out-of-date ## Tests) /docs
Reconciling docs/reference/* after a runner/schema change already merged /docs

Flow

X-1. Scan for drift

  • git diff/git log since the last doc touch; check the CHANGELOG against recent merges (issue links present? ### fixes/changes/… correct?).
  • FAQ: scan docs/faq/faq.md against current features per help-faq.md — any user-visible surface (engine support, auth/billing, privacy, approval semantics, cost, voice, install/update) answered wrongly?
  • CLAUDE.md ## Tests: does the list match tests/ reality? Any new test file undocumented?
  • docs/reference/*: any runner/schema/telegram doc lagging code?

Read the full file on GitHub · 84 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. yesterday First seen · 84 lines · 27 tokens per session scan A c77fa2995431

Subscribe to this mod's changes

docs is a command published in the GitHub repository littlebearapps/untether (66 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 1,110 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.