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-collectorgit 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.03174 |
| Opus 5 | $0.00000 | $0.01587 |
| Sonnet 5 | $0.00000 | $0.00635 |
| Haiku 4.5 | $0.00000 | $0.00317 |
Grade A, and why
release-note-collector 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 — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Collector Release Note
Automates the creation of Collector release notes for Installed Collector versions and OpenTelemetry features.
What this command does
When you invoke release-note-collector, Claude will guide you through:
- Determine release type. Installed Collector version or OpenTelemetry feature
- Gather release details. Version number, changes, features, or fixes
- Create markdown file. Generate file with proper frontmatter and structure
- Format content. Apply correct formatting for version releases or features
- Validate and preview. Check structure and provide next steps
When to use this command
- Publishing new Installed Collector versions with bug or security fixes.
- Announcing OpenTelemetry collector features and improvements.
- Documenting collector version updates.
- Releasing new OpenTelemetry integrations or capabilities.
Release types
Installed Collector Release (-installed.md)
For Installed Collector version releases:
- Version numbers: Format X.Y.Z-N (e.g., 19.535-6).
- Security fixes: CVE patches, dependency upgrades.
- Bug fixes: Issue resolutions and stability improvements.
- Minor features: Small enhancements in collector behavior.
Typical cadence: As needed when versions ship
OpenTelemetry Release (-otel.md)
For OpenTelemetry collector features:
- New features: Installation methods, integrations, capabilities.
- Improvements: Performance enhancements, reliability updates.
- Announcements: CDN changes, configuration updates.
Typical cadence: As features are released
Workflow
Step 1: Gather information
Ask the user for:
For Installed Collector releases:
- Version number: Full version (e.g., 19.535-6).
- Release date: Date in YYYY-MM-DD format.
- Changes: List of security fixes, bug fixes, or features.
For OpenTelemetry releases:
- Feature name: Name of the feature or update.
- Release date: Date in YYYY-MM-DD format.
- Description: What it does and why it matters (2-3 sentences).
- Documentation link: Relative path to the doc.
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 · 405 lines · 0 tokens per session scan A 169b9a666a7d
release-note-collector 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 3,174 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.