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/remove-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.01574 |
| Opus 5 | $0.00000 | $0.00787 |
| Sonnet 5 | $0.00000 | $0.00315 |
| Haiku 4.5 | $0.00000 | $0.00157 |
Grade A, and why
remove-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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remove or Move Doc — Safe Deprecation Workflow
Automates the complete workflow for removing or moving a Sumo Logic doc while preventing broken links and maintaining SEO health.
What this command does
When you invoke /remove-doc, Claude will guide you through:
- Create 301 redirect. Add redirect mapping to
cid-redirects.json. - Update internal links. Find and replace all references to the old URL.
- Remove from hub pages. Delete card from parent
index.mdand Product List. - Delete the doc file. Remove the actual markdown file.
- Remove from navigation. Delete entry from
sidebars.ts. - Optional steps. Add deprecation notes, hide from search engines.
When to use this command
- Deprecating legacy docs in favor of new versions.
- Consolidating duplicate content.
- Removing outdated documentation.
- Moving docs to new locations.
Workflow
Step 1: Gather information
Ask the user for:
- Old doc path: The file path being removed (e.g.,
docs/integrations/web-servers/nginx-legacy.md). - New doc path: The replacement doc path (e.g.,
docs/integrations/web-servers/nginx.md). - Reason: Why the doc is being removed (for context).
Step 2: Create 301 redirect
- Read
cid-redirects.json. - Convert the old file path to a URL path (remove
docs/prefix, remove.mdextension). - Convert the new file path to a URL path.
- Add the redirect mapping:
"/docs/old-path": "/docs/new-path", - Validate JSON syntax after adding.
Safety check: Ensure the new doc path actually exists before creating the redirect.
Step 3: Update internal links
- Use Grep to search for references to the old URL across all docs:
- Search for the old file path (without
docs/and.md). - Search for relative path variations.
- Search for
useBaseUrlreferences.
- Search for the old file path (without
- Show the user all files that reference the old URL.
- For each file, replace old URL with new URL (one by one, not Find All > Replace All).
- Check for references in:
- Other markdown docs.
- Parent hub/index pages.
- Product List (
docs/integrations/product-list/).
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 · 199 lines · 0 tokens per session scan A d8dcc054a96a
remove-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 1,574 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.