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/c2c-source-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.02470 |
| Opus 5 | $0.00000 | $0.01235 |
| Sonnet 5 | $0.00000 | $0.00494 |
| Haiku 4.5 | $0.00000 | $0.00247 |
Grade A, and why
c2c-source-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 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.
How it starts
The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
new-c2c-source-doc
Create a new Cloud-to-Cloud integration source documentation page with proper structure, navigation, and redirects.
Usage
/new-c2c-source-doc
Overview
This command automates the creation of Cloud-to-Cloud (C2C) source documentation by:
- Creating a properly structured doc file from the template
- Adding the source to the sidebar navigation
- Creating a CID redirect mapping
- Including all expected frontmatter and sections
Prerequisites
Before running this command, you should have:
- Vendor name and icon/logo URL
- List of data sources and polling intervals
- Vendor configuration prerequisites (if applicable)
- Source configuration steps for Sumo Logic UI
- Metadata fields information
- JSON schema configuration parameters
- Fed deployment availability status
Process
Step 1: Gather Information
Ask the user for the following information using AskUserQuestion:
Question 1: "What is the vendor/product name?"
- Header: "Vendor Name"
- Options:
- "I'll provide it in text" (description: "Enter the full vendor/product name exactly as it should appear")
- Note: Use the "Other" option that's automatically provided
Question 2: "What is the icon URL for this source?"
- Header: "Icon URL"
- Options:
- "Use S3 app icons URL" (description: "Format: https://app_icons.s3.amazonaws.com/{vendor}.svg")
- "I'll provide a custom URL" (description: "Provide the full HTTPS URL to the icon")
Question 3: "Is this source available in Fed deployment?"
- Header: "Fed Deployment"
- Options:
- "Not available" (description: "Include note that source is not available in Fed deployment")
- "Available" (description: "Source is available in Fed deployment, no note needed")
- "Unknown" (description: "Check with team and include the not-available note for now")
Question 4: "Do you have the vendor configuration details ready?"
- Header: "Vendor Config"
- Options:
- "Yes, I'll provide them" (description: "I have prerequisites and vendor UI setup steps")
- "No, I'll add them later" (description: "Leave placeholder comments in the template")
- "Not applicable" (description: "This source does not require vendor-side configuration")
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.
- 2d ago First seen · 254 lines · 0 tokens per session scan A 933642ec3eb7
c2c-source-doc is a command published in the GitHub repository SumoLogic/sumologic-documentation (42 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,470 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.