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 everywan-dev/claude-code-engineeringnpx agentmods add plugins/everywan-dev/claude-code-engineering/marketplacegit clone --depth 1 https://github.com/everywan-dev/claude-code-engineeringGrade A, and why
everywan 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": "everywan",
"owner": {
"name": "everyWAN",
"url": "https://everywan.com"
},
"description": "Engineering skills and review agents for Claude Code, built on one rule: a check that cannot fail is not a check.",
"plugins": [
{
"name": "claude-code-engineering",
"source": "./",
"description": "Turn Claude Code into a team that has to prove it: 44 skills, 8 review agents, a router that decides how much validation a change needs, and a knowledge layer where nothing is asserted without a check that could have failed.",
"category": "engineering",
"keywords": [
"engineering",
"skills",
"code-review",
"tdd",
"root-cause-analysis",
"documentation",
"verification",
"devops"
]
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 27 lines scan A fff7b96fc19e
everywan is a plugin published in the GitHub repository everywan-dev/claude-code-engineering (2 stars, last pushed 13d ago), 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
scaccogatto
Claude Code plugins by scaccogatto.
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
scraps-migration
LLM migration workflows for moving Scraps wikis from v0 to v1. Runs version-pinned audits, converts tag and config syntax, and verifies the result with v1 lint/build.
wikimate-marketplace
Plugin marketplace listing 1 plugin: wikimate.
forge-harness
Plugin marketplace listing 2 plugins: fh-meta, fh-commons.
hipocampus
Persistent agent memory that survives across sessions — auto-compacting 3-tier memory with hybrid search. Your agent remembers what it learned, decided, and built.