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.
git clone --depth 1 https://github.com/YusenZhang0601/context-canopyWrote 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/yusenzhang0601/context-canopy/mcp)<a href="https://agentmods.dev/plugins/yusenzhang0601/context-canopy/mcp"><img src="https://agentmods.dev/badge/plugins/yusenzhang0601/context-canopy/mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/yusenzhang0601/context-canopy/mcp"><img src="https://agentmods.dev/badge/plugins/yusenzhang0601/context-canopy/mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
context-canopy 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 1mo ago.
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": "context-canopy",
"version": "1.0.2",
"displayName": "ContextCanopy",
"description": "Portable personal AI context: search and capture knowledge, then read allowlisted user authority across agents",
"author": "TonyRainforest",
"license": "MIT",
"mcp": {
"type": "stdio",
"command": "node",
"args": ["${pluginDir}/index.js"],
"env": {}
},
"skills": [
{
"name": "capture-knowledge",
"path": "skills/capture-knowledge/SKILL.md"
}
],
"categories": ["productivity", "knowledge-management"],
"tags": ["personal-ai", "agent-memory", "agent-portability", "cross-agent-memory", "knowledge-base", "local-first", "mcp", "obsidian"],
"icon": "📚",
"permissions": {
"filesystem": {
"read": [
"${pluginDir}/../vault/01-Knowledge",
"${pluginDir}/../vault/02-Insights",
"${pluginDir}/../vault/03-Personal",
"${pluginDir}/../vault/04-Sources",
"${pluginDir}/../vault/90-System"
],
"write": [
"${pluginDir}/../vault/01-Knowledge",
"${pluginDir}/../vault/04-Sources",
"${pluginDir}/../vault/90-System"
],
"reason": "Read the complete canonical graph and fixed personal-AI authority files for compiler checks and context tools; write source captures, Knowledge owners, semantic review registry, derived indexes, and maintenance log"
}
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 92 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.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.
- 1mo ago First seen · 41 lines scan A 254f9fa6e9ff
context-canopy is a plugin published in the GitHub repository YusenZhang0601/context-canopy (2 stars, last pushed 16d 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
keymem
Associative long-term memory — recall by key-graph association, plus passive memory surfacing on every prompt.
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.
ownmem
Git-native project memory for AI coding agents, with deterministic local recall, evidence gates, and layered delivery that quotes, points, or abstains.
engraphis-memory
Give agents durable, scoped, explainable memory across sessions and repos via the Engraphis MCP tools. Use when you learn something worth keeping, need prior context before acting, or ask why/how a fact changed. Covers remember/recall, why/timeline, forget/pin/correct, sessions, and code search.
graft
Persistent local memory for coding agents: recall past fixes, decisions and gotchas before solving them again, and save what was learned.
autograph
Schema-as-code memory engine for Obsidian vaults that AI agents write to: typed cards, entity dedup, link repair, update-in-place (supersede + History), Ebbinghaus decay, MOC generation, and a vault health score. Plain Markdown you own, Python stdlib only. Ships the autograph skill plus a /research slash command that…