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.
/plugin marketplace add slnu21/Pawsenpx agentmods add plugins/slnu21/pawse/marketplacegit clone --depth 1 https://github.com/slnu21/PawseGrade A, and why
leo 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.
What it actually says
{
"name": "leo",
"owner": { "name": "sinwoo0225" },
"description": "Leo's marketplace — home of pawse, the interactive desktop hook widget for Claude Code (Windows).",
"plugins": [
{
"name": "pawse",
"source": "./plugin",
"description": "Interactive desktop hook widget for Claude Code (Windows)."
}
]
}
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 · 13 lines scan A fd945287560a
leo is a plugin published in the GitHub repository slnu21/Pawse (1 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
credential-guard
Protect secrets and credentials from Claude Code. Blocks writes to .env files, detects API keys in shell commands, prevents hardcoded tokens, and guards service account JSON files.
git-protection
Git safety hooks for Claude Code. Blocks force-push, protects the main/master branch, prevents hard-reset, blocks git clean, and blocks forced branch deletion.
token-guard
Token consumption guards for Claude Code. Warns on large file reads (100KB+), limits unique file reads per session, estimates token budget, and caps subagent spawns. From 800+ hours of autonomous operation data.
cc-safe-setup
909 safety hooks for Claude Code — prevent file deletion, credential leaks, git disasters, and token waste during autonomous AI coding sessions.
claude-bell
Notification sounds for Claude Code: a gentle chime when Claude needs you, so you can safely switch away.
claude-bell
Gentle notification sounds: a rising two-note chime when Claude needs your confirmation, a resolved major arpeggio when a task completes. Sounds are user-replaceable.