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 Cloud-Forest-Analytics/evergreennpx agentmods add plugins/cloud-forest-analytics/evergreen/marketplacegit clone --depth 1 https://github.com/Cloud-Forest-Analytics/evergreenGrade A, and why
evergreen 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
{
"$schema": "https://json.schemastore.org/claude-code-marketplace.json",
"name": "evergreen",
"owner": { "name": "Cloud Forest Analytics" },
"description": "Evergreen — self-maintenance + a weekly newsletter for any repo. This repository is both the plugin and its own marketplace.",
"plugins": [
{
"name": "evergreen",
"source": "./",
"description": "Keep any repo evergreen: a weekly newsletter (weekly-seedling) + start/end-of-day board & DORA hygiene. Zero infra.",
"license": "MIT",
"category": "automation",
"keywords": ["maintenance", "newsletter", "dora", "repo-hygiene"]
}
]
}
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 · 17 lines scan A 413f97c8d756
evergreen is a plugin published in the GitHub repository Cloud-Forest-Analytics/evergreen (1 stars, last pushed 2mo 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
feedoracle-compliance
Real-time MiCA regulatory compliance and RWA risk intelligence for AI agents. 27 tools across compliance, risk, evidence, KYA, and audit verification — 19 MiCA articles, 105+ stablecoins. Cryptographically signed, audit-ready responses.
lumail
Plugin marketplace listing 1 plugin: lumail.
lumail
Lumail plugin for Claude Code. Manage subscribers, draft campaigns, build workflow sequences, and read email analytics from your terminal.
norma-mcp-server
EU compliance corpus across 8 frameworks via MCP — free, hosted by Kynosure.
buttondown-skill
Buttondown newsletter management - create drafts, schedule emails, view analytics.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.