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/release-note-csoargit 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.05043 |
| Opus 5 | $0.00000 | $0.02521 |
| Sonnet 5 | $0.00000 | $0.01009 |
| Haiku 4.5 | $0.00000 | $0.00504 |
Grade A, and why
release-note-csoar 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 — 606 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Cloud SOAR Release Note
Automates the creation of Cloud SOAR (Automation Service) release notes for platform updates, integration changes, and bug fixes.
What this command does
When you invoke release-note-csoar, Claude will guide you through:
- Determine release type. Content Release or Application Update
- Gather release details. Date, changes, integrations, playbooks, or platform updates
- Create markdown file. Generate file with proper frontmatter and structure
- Format content. Apply correct formatting for the release type
- Validate and preview. Check structure and provide next steps
When to use this command
- Publishing new integrations and playbooks (Content Release)
- Publishing Cloud SOAR platform updates (Application Update)
- Documenting integration updates or bug fixes
- Announcing new API endpoints or features
- Releasing playbook improvements
Release types
Content Release (-content-release.md)
For releases focused on new content (integrations and playbooks):
- New integrations: Brand new integrations added to App Central
- Updated integrations: Improvements to existing integrations
- New playbooks: New playbooks with ID numbers and titles
- Simple format: Just lists of what's new/updated, minimal descriptions
Typical cadence: Monthly or as content batches are released
Application Update (-application-update.md)
For platform features, enhancements, and bug fixes:
- Platform features: New capabilities, UX improvements, APIs
- Integration changes: With detailed descriptions of what changed
- Bug fixes: Issues resolved in integrations, platform, or playbooks
- Detailed format: Sections with descriptions and context
Typical cadence: Monthly, published early the following month
Release structure (varies by type)
Content Release Structure
Simple format with just lists:
- Intro paragraph - Brief description of release
- Integrations (H3) - Bulleted list of [New]/[Updated] integrations
- Playbooks (H3) - Bulleted list of [New] playbooks with IDs and titles
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 · 606 lines · 0 tokens per session scan A faf9d43ef0a0
release-note-csoar 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 5,043 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.