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/sumulige/sumulige-claude/prgit clone --depth 1 https://github.com/sumulige/sumulige-claudeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/sumulige/sumulige-claude/pr)<a href="https://agentmods.dev/commands/sumulige/sumulige-claude/pr"><img src="https://agentmods.dev/badge/commands/sumulige/sumulige-claude/pr.svg" alt="Measured on agentmods" height="20"></a>What 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.00008 | $0.00322 |
| Opus 5 | $0.00004 | $0.00161 |
| Sonnet 5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
pr 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 3d 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.
What it actually says
Create or update a pull request with proper documentation.
Step 1: Check Current State
git status
git log -5 --oneline
git branch --show-current
Step 2: Check for Existing PR
gh pr list --head $(git branch --show-current)
Step 3: Create PR (if none exists)
Analyze Changes
# Get commit history since branch from main/master
git diff $(git merge-base main HEAD)..HEAD --stat
# Get detailed diff
git diff $(git merge-base main HEAD)..HEAD
Create PR with Template
Use gh pr create with:
## Summary
<!-- 2-3 bullet points describing the main changes -->
## Changes
<!-- Detailed list of changes -->
## Test Plan
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing completed
- [ ] Documentation updated
## Checklist
- [ ] Code follows project style guidelines
- [ ] Self-review completed
- [ ] Comments added to complex code
- [ ] Documentation updated
- [ ] No new warnings generated
Step 4: Update PR (if exists)
If PR already exists, ask user if they want to:
- Update description
- Add comments
- Request review
- Merge if ready
Step 5: Show Result
Display PR URL and check CI status:
gh pr checks
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.
- 3d ago First seen · 77 lines · 8 tokens per session scan A af8dac578cbc
pr is a command published in the GitHub repository sumulige/sumulige-claude (2 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 322 once invoked, about $0.0000 per session on Opus 5. 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-31.
Other commands, from other repositories
doctor
Run read-only health checks on the Kobiton automate plugin (CLI, credentials, profile).
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
handoff
Force a session catchup or a memory promotion outside the hook lifecycle. Default is catchup (read-only); promote is HITL gated.
gate
You are the Gate System controller. Execute quality gate reviews based on the user's request.