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-csegit 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.03140 |
| Opus 5 | $0.00000 | $0.01570 |
| Sonnet 5 | $0.00000 | $0.00628 |
| Haiku 4.5 | $0.00000 | $0.00314 |
Grade A, and why
release-note-cse 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 — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Cloud SIEM Release Note
Automates the creation of Cloud SIEM (CSE) release notes with proper formatting, frontmatter, and structure.
What this command does
When you invoke release-note-cse, Claude will guide you through:
- Determine release type. Content release or Application release
- Gather release details. Date, changes, features, bug fixes
- Create markdown file. Generate file with proper frontmatter and structure
- Format content. Apply correct formatting for rules, mappers, parsers, or features
- Validate and preview. Check structure and provide next steps
When to use this command
- Publishing Cloud SIEM content updates (rules, log mappers, parsers).
- Announcing new Cloud SIEM features or bug fixes.
- Creating regular bi-weekly or monthly CSE release notes.
- Documenting Cloud SIEM application updates.
Release types
Content Release (-content.md)
For updates to Cloud SIEM detection content:
- Rules: New or updated detection rules
- Log Mappers: New or updated log mapping configurations
- Parsers: Parser updates and enhancements
- Schema changes: New fields or tags
Typical cadence: Every 1-2 weeks
Application Release (-application.md)
For Cloud SIEM product features and updates:
- New features: UI improvements, new capabilities
- Bug fixes: Issue resolutions
- Performance improvements: Optimizations
- Breaking changes or deprecations.
Typical cadence: As needed when features ship
Workflow
Step 1: Gather information
Ask the user for:
Required:
- Release type: Content or Application
- Release date: Date in YYYY-MM-DD format
- Changes: List of what's included
For Content Releases:
- New/updated rules (rule IDs and names).
- New/updated log mappers.
- New/updated parsers.
- Brief summary of changes.
For Application Releases:
- Feature name and description.
- Documentation links.
- Screenshots (if applicable).
- Any breaking 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.
- 2d ago First seen · 420 lines · 0 tokens per session scan A 9ec8b425745a
release-note-cse 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 3,140 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.