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/testgit 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/test)<a href="https://agentmods.dev/commands/sumulige/sumulige-claude/test"><img src="https://agentmods.dev/badge/commands/sumulige/sumulige-claude/test.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.00006 | $0.00222 |
| Opus 5 | $0.00003 | $0.00111 |
| Sonnet 5 | $0.00001 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
test 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
Run the test suite and provide comprehensive results.
Step 1: Detect Test Framework
Check what test framework is being used:
cat package.json | grep -E '"test"|"jest"|"vitest"|"mocha"|"pytest"'
Step 2: Run Tests
Run the appropriate test command:
# Node.js / JavaScript
npm test
# Python
pytest
# Rust
cargo test
# Go
go test ./...
Step 3: Show Coverage
If coverage is available, run:
npm run test:coverage
# or
pytest --cov
Step 4: Analyze Results
Provide a summary:
- Total tests run
- Pass/fail counts
- Coverage percentage
- Any failing tests with details
Step 5: Fix Failures (if any)
If tests fail, help the user:
- Identify the root cause
- Fix the issue
- Re-run tests to verify
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 · 57 lines · 6 tokens per session scan A e9fb08d71ef4
test is a command published in the GitHub repository sumulige/sumulige-claude (2 stars, last pushed 6mo ago), licensed MIT. It adds 6 tokens to every session and 222 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
work
通过 v3 流程发起正式工作请求 (entry gate).
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.specify
Create or update the feature specification from a natural language feature description.
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.