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/clawsouls/clawsouls-claude-code-plugin/browsegit clone --depth 1 https://github.com/clawsouls/clawsouls-claude-code-pluginWrote 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/clawsouls/clawsouls-claude-code-plugin/browse)<a href="https://agentmods.dev/commands/clawsouls/clawsouls-claude-code-plugin/browse"><img src="https://agentmods.dev/badge/commands/clawsouls/clawsouls-claude-code-plugin/browse.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.00011 | $0.00133 |
| Opus 5 | $0.00005 | $0.00067 |
| Sonnet 5 | $0.00002 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
browse 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 4d 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
Browse ClawSouls Personas
Search and browse agent personas on ClawSouls (the Soul Spec marketplace).
Use the soul_search MCP tool to find personas matching "$ARGUMENTS".
If no arguments provided, list the most popular personas.
For each result, show:
- Name: owner/name
- Description: what the persona does
- Grade: SoulScan safety grade (if available)
After showing results, ask if the user wants to install any persona. If yes, use the soul_install MCP tool.
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.
- 4d ago First seen · 19 lines · 11 tokens per session scan A ff3f86c388d3
browse is a command published in the GitHub repository clawsouls/clawsouls-claude-code-plugin (2 stars, last pushed 23d ago), licensed Apache-2.0. It adds 11 tokens to every session and 133 once invoked, about $0.0001 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
setup
Set up Postman MCP Server. Authenticate via OAuth or API key, verify connection, select workspace.
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
refine-title
深度分析 Issue 或 PR 内容，并将其标题重构为 Conventional Commits 格式.
get-flow-run
Inspect a Postman Flow run by its Run ID — per-block logs, failing block, and status.
warden-cost
Dollar accounting — what does each active rule actually save, in money? Translates the token-measured verdict into dollars using a price table and the agent's own token-type mix, with a per-session net and a break-even. Read-only; spends no tokens.
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.