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 fatmo666/Caushellnpx agentmods add plugins/fatmo666/caushell/claude-codegit clone --depth 1 https://github.com/fatmo666/CaushellGrade A, and why
caushell-claude 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": "caushell-claude",
"version": "0.0.9",
"description": "Session-aware shell guardrails for Claude Code backed by the Caushell runtime.",
"author": {
"name": "Caushell"
},
"homepage": "https://github.com/fatmo666/Caushell",
"repository": "https://github.com/fatmo666/Caushell",
"license": "Apache-2.0",
"userConfig": {
"hook_path": {
"type": "file",
"title": "caushell-claude-hook path",
"description": "Optional explicit path to the native caushell-claude-hook executable. If unset, caushell-claude uses CAUSHELL_CLAUDE_HOOK_PATH, caushell-claude-hook on PATH, CAUSHELL_REPO_ROOT, or a source checkout target/debug path."
},
"runtime_path": {
"type": "file",
"title": "caushell path",
"description": "Optional explicit path to caushell. If unset, caushell-claude resolves caushell from PATH."
},
"store_root": {
"type": "directory",
"title": "Session store root",
"description": "Directory where Caushell persists Claude session events and snapshots"
},
"socket_root": {
"type": "directory",
"title": "Socket root",
"description": "Directory for per-workspace Caushell daemon sockets and logs"
}
}
}
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 · 34 lines scan A 9d2385a228bb
caushell-claude is a plugin published in the GitHub repository fatmo666/Caushell (6 stars, last pushed yesterday), licensed Apache-2.0. 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
agmsg
Cross-agent messaging via SQLite. Send messages between CLI AI agents. No daemon, no network.
probity
Plugin marketplace listing 1 plugin: probity.
ngernthongdee
Ngernthongdee's Claude Code plugins — starting with devenv-doctor, a dev environment health check that tells you exactly what's broken and how to fix it.
dcotelo
Per-repository Claude account switching: keep personal and work subscriptions separate.
codoop-flow
In-session orchestration for the codoop-flow Agent-Centric ticket pipeline: pick -> build -> verify -> review -> ship, driven by a skill plus a deterministic guardrail CLI.
agent-messaging
Agent Messaging Protocol (AMP) - Secure, cryptographically signed messaging between AI agents across different providers.