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 skarn-security/agent-guardnpx agentmods add plugins/skarn-security/agent-guard/claudegit clone --depth 1 https://github.com/skarn-security/agent-guardGrade A, and why
skarn-guard 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": "skarn-guard",
"version": "0.27.0",
"description": "Real-time guard on five Claude Code pre-execution hook events (tool calls, permission decisions, submitted and expanded prompts, and subagent creation) plus a response-end advisory that flags an action leaking a secret, installing a malicious package, or exfiltrating data, plus the skarn-audit skill (scan sessions and vet configs, redacted). Ships in audit mode, which reports the verdict and never changes what the agent does; blocking needs enforce mode and a registered license. Backed by the Skarn detection engine.",
"author": {
"name": "Skarn",
"url": "https://getskarn.com"
},
"homepage": "https://getskarn.com",
"repository": "https://github.com/skarn-security/agent-guard",
"license": "MIT",
"keywords": [
"security",
"secrets",
"guard",
"skills",
"audit"
]
}
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 · 20 lines scan A 6ccf2c94dc05
skarn-guard is a plugin published in the GitHub repository skarn-security/agent-guard (31 stars, last pushed 4d 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-30.
Other plugins, from other repositories
shopify-plugin
Shopify developer tools for Claude Code — search Shopify docs, generate and validate GraphQL, Liquid, and UI extension code. Skill scripts send usage telemetry (queries, code, model/client identifiers) to shopify.dev by default; set OPTOUTINSTRUMENTATION=true, or create an empty file at /.config/shopify-ai-toolkit/o.
writing-skills
Plugin marketplace listing 1 plugin: writing-skills.
frane-vibesurfer
vibesurfer (vs) — agent-native headless browser.
goalkeeper
Durable goal-following for Claude Code: contracts with definition-of-done, subagent judge gates, and linear chains.
noisy-tools-in-subagent
Forces noisy commands (builds, tests, linters, static analysis) to run inside a Sonnet subagent instead of the main context, preserving main-agent tokens.
forge
A generator: it interviews an organization and emits a standalone, org-owned Claude Code plugin (the org's agent harness) aligned to how that org actually works. Karpathy-schema wiki + role/subagent pattern + skill verbs + tool adapters + the operating model. Re-emit to upgrade; never fork.