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/sumologic/sumologic-documentation/audit-docgit clone --depth 1 https://github.com/SumoLogic/sumologic-documentationWhat 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.02647 |
| Opus 5 | $0.00000 | $0.01324 |
| Sonnet 5 | $0.00000 | $0.00529 |
| Haiku 4.5 | $0.00000 | $0.00265 |
Grade A, and why
audit-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.
How it starts
The opening of the file, as written. The whole thing — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Doc — Documentation Quality Check
Use this command to audit a doc for Sumo Logic style, structure, links, and frontmatter compliance — run it before submitting any PR, after creating a new doc, or when reviewing community contributions.
Gotchas
- H1 headings and the
titlefrontmatter field use Title Case. H2, H3, H4 use sentence case (only first word and proper nouns capitalized). - Skip warnings for legacy docs with an established style, docs tagged
noindex(temporary drafts), or third-party content not meant to be modified. /audit-docdoes not check SEO/AEO/GEO signals — run/seo-auditseparately for discoverability.
When to use this command
- Before submitting a PR to check doc quality
- After creating a new doc to validate structure
- When updating existing docs to ensure consistency
- To identify broken links or missing images
- When reviewing community contributions
Workflow
Step 1: Identify the doc to audit
Ask the user for:
- File path: Full path to the markdown file to audit
- Doc type (optional): App, feature, how-to, concept, reference, release note
- Strictness level (optional): Lenient, standard, or strict
If no file path provided, ask user to specify the file.
Step 2: Read the file
Use the Read tool to read the complete file content.
Step 3: Analyze frontmatter
Check for required fields and proper formatting:
Universal requirements:
-
idfield present and matches filename (without .md) -
titlefield present, Title Case, under 60 characters - No frontmatter syntax errors (proper YAML format)
For docs (not release notes):
-
descriptionfield present, 140–160 characters (Warning if under 100 or over 160; Suggestion if 100–139) - Description starts with "The Sumo Logic..."
-
sidebar_label(if present) is shorter than title
For app docs:
-
imagefield with valid S3 URL or local path -
tagsincludes "apps" and vendor slug
For release notes:
-
hide_table_of_contents: truepresent -
imageuses standard Sumo Logic preview URL -
keywordspresent (unless Collector type)
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 · 375 lines · 0 tokens per session scan A 9c4ba51e8112
audit-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,647 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.
Other commands, from other repositories
add-scaffold
按 14-phase 工作流为指定 app 编写清理 scaffold（含需求采集、实测勘测、TOML、safety test、UI 集成）.
scaffold-review
Command "scaffold-review" from cccyd2003-qwq/pinkbin, covering 诊断 checklist, phase 1-2 类别需求, phase 5-7 实测勘测, phase 8 toml 本身 and phase 10 safety test.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
loci-scan
Refresh the current project's local Loci memory.
adr-supersede
Create a new ADR that supersedes an existing one.
spec-forge
Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.