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/doc-from-jiragit 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.02697 |
| Opus 5 | $0.00000 | $0.01349 |
| Sonnet 5 | $0.00000 | $0.00539 |
| Haiku 4.5 | $0.00000 | $0.00270 |
Grade A, and why
doc-from-jira 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc from Jira — Scaffold a Doc from a Jira Ticket
Pulls a Jira ticket from the DOCS project, extracts the content requirements, and scaffolds a fully structured documentation file ready for writing. Eliminates the blank-page problem and keeps the doc aligned with the ticket spec from the start.
What this command does
When you invoke /doc-from-jira, Claude will:
- Fetch the Jira ticket. Pull title, description, acceptance criteria, and linked resources
- Determine doc type. Feature, how-to, concept, reference, or troubleshooting
- Infer the file path. Based on the technical area and content type
- Scaffold the doc. Generate a file with correct frontmatter, structure, and placeholder sections pre-populated from the ticket
- Update sidebars.ts. Add the new doc to navigation (with user approval)
- Link back to Jira. Set the Jira ticket to In Progress if not already
When to use this command
- Starting a new doc for a DOCS ticket
- When a ticket has a detailed description or acceptance criteria worth preserving
- For tickets with linked specs, PRDs, or engineering docs to pull context from
- When you want to ensure the doc structure is aligned with what was requested
When NOT to use this command
- App integrations — use
/app-docinstead - Cloud-to-Cloud sources — use
/c2c-source-docinstead - Release notes — use the appropriate
/release-note-*command instead - Tickets that do not require a net-new doc (pure updates, typo fixes)
Workflow
Step 1: Get the ticket number
If the user provides a ticket number (e.g., DOCS-1234), use it directly.
If the user says "use my current ticket" or "use the branch ticket", extract the ticket number from the current git branch name (pattern: DOCS-\d+).
If no ticket is found, ask the user for the ticket number.
Step 2: Fetch the ticket
Use the Jira MCP tool to fetch the ticket:
- Cloud ID:
247075db-3b0b-4f1b-92db-51683ab743a6 - Issue key: the provided DOCS-XXXX number
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 · 360 lines · 0 tokens per session scan A 996568f4de3a
doc-from-jira 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,697 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.