A command that creates a new documentation file with its metadata, structure, and sidebar entry. It supports feature guides, how-to instructions, concept explanations, reference pages, and troubleshooting guides.

Use it when adding general product documentation, tutorials, conceptual explanations, reference material, or troubleshooting content.

It avoids manually setting up the files and navigation needed for a new document and helps choose the right document type.

doc — Command by SumoLogic

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/sumologic/sumologic-documentation/doc

Clone the repo

git clone --depth 1 https://github.com/SumoLogic/sumologic-documentation

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,628 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.02628
Opus 5	$0.00000	$0.01314
Sonnet 5	$0.00000	$0.00526
Haiku 4.5	$0.00000	$0.00263

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

Security

Grade A, and why

doc 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/doc.md · 429 lines

How it starts

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

Create New Doc

Use this command to create a new feature doc, how-to, concept, reference, or troubleshooting guide — it scaffolds the file, frontmatter, structure, and sidebar entry.

When to use this command

Creating feature documentation.
Writing how-to guides and tutorials.
Documenting concepts and reference material.
Creating troubleshooting guides.
Adding general content that does not fit specialized templates (apps, sources, release notes).

When NOT to use this command

App integrations. Use app-doc instead.
Cloud-to-Cloud sources. Use c2c-source-doc instead.
Release notes. Use release-note-cse or release-note-collector instead.

Doc types

Feature Documentation

Announces and explains product capabilities.
Covers what it does, why it matters, how to use it.
Includes configuration steps and examples.

How-to Guide

Step-by-step instructions for specific tasks.
Focuses on practical outcomes.
Includes prerequisites and validation steps.

Concept

Explains ideas, architecture, or background information.
Provides context for using features.
Educational and explanatory.

Reference

Detailed technical specifications.
API endpoints, configuration parameters, field lists.
Structured data meant for lookup.

Troubleshooting

Diagnoses and resolves common issues.
Problem-symptom-solution format.
Includes error messages and fixes.

Workflow

Step 1: Gather information

Ask the user for:

Required:

Doc type: Feature, how-to, concept, reference, or troubleshooting.
Title: Page title in Title Case (60 characters max for SEO).
File path: Where to save the file (e.g., docs/manage/security/access-keys.md).
Description: One or two sentences for search engines and metadata.

Optional:

Keywords: Terms for SEO and search (3-5 recommended).
Sidebar label: Alternative text for sidebar navigation (if different from title).
CID needed: Whether this doc needs a permanent URL for UI links.
Hub page: Whether to add a card to a parent index page.

Read the full file on GitHub · 429 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.

yesterday First seen · 429 lines · 0 tokens per session scan A a247b0016670

Subscribe to this mod's changes

doc is a command published in the GitHub repository SumoLogic/sumologic-documentation (42 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,628 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-30.

Debugging Frontend Learning and teaching ReAct documentation open-source

doc

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Create New Doc

When to use this command

When NOT to use this command

Doc types

Feature Documentation

How-to Guide

Concept

Reference

Troubleshooting

Workflow

Step 1: Gather information

What this file has done since we first saw it

Other commands, from other repositories

add-scaffold

reflect

loci-settings

project-health

doncheli-close

OPSX: Onboard