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 coltonbearden/carrelnpx agentmods add plugins/coltonbearden/carrel/carrel-watchgit clone --depth 1 https://github.com/coltonbearden/carrelWrote 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/plugins/coltonbearden/carrel/carrel-watch)<a href="https://agentmods.dev/plugins/coltonbearden/carrel/carrel-watch"><img src="https://agentmods.dev/badge/plugins/coltonbearden/carrel/carrel-watch.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
carrel-watch 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 today.
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": "carrel-watch",
"description": "Watch folders and run carrel actions on file events: /watch-folder plus a watch-automation recipe skill.",
"version": "0.1.2",
"author": { "name": "Colton Bearden" },
"license": "MIT",
"keywords": ["files", "watch", "automation", "watchdog", "folder-actions"]
}
What it installs
The manifest is a name and a version. 1 skill, 1 command travel with it, and installing the plugin installs all of them — 73 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- today Changed 9d4b75a35267
- 3d ago First seen · 9 lines scan A b2a917acf81c
carrel-watch is a plugin published in the GitHub repository coltonbearden/carrel (1 stars, last pushed today), 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
api-authentication
Secure API authentication with JWT, OAuth 2.0, API keys. Use for authentication systems, third-party integrations, service-to-service communication, or encountering token management, security headers, auth flow errors.
cloudflare-sandbox
Cloudflare Sandboxes SDK for secure code execution in Linux containers at edge. Use for untrusted code, Python/Node.js scripts, AI code interpreters, git operations.
csrf-protection
Implements CSRF protection using synchronizer tokens, double-submit cookies, and SameSite attributes. Use when securing web forms, protecting state-changing endpoints, or implementing defense-in-depth authentication.
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
reflect
Better alignment with LLMs.
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.