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 eriknewton/sanctuary-frameworknpx agentmods add plugins/eriknewton/sanctuary-framework/plugingit clone --depth 1 https://github.com/eriknewton/sanctuary-frameworkGrade A, and why
sanctuary-framework 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": "sanctuary-framework",
"version": "0.3.0",
"description": "The open source standard for secure, private AI: operating-system enforcement is live on macOS today; Linux and Windows are not live enforcement yet, and your data stays under your own keys with current portability bounds called out in the Assurance Matrix. Wraps any MCP-compatible agent with encrypted state, approval gates, a portable identity and reputation, and an audit tool that finds security and privacy gaps in your current setup.",
"author": {
"name": "Erik Newton",
"homepage": "https://github.com/eriknewton/sanctuary-framework"
},
"license": "Apache-2.0",
"keywords": [
"security",
"egress-control",
"encryption",
"identity",
"reputation",
"privacy",
"mcp",
"agent",
"openclaw",
"audit",
"zero-knowledge"
]
}
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 · 24 lines scan A 189e3c8b5f6a
sanctuary-framework is a plugin published in the GitHub repository eriknewton/sanctuary-framework (8 stars, last pushed yesterday), 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
anolisa-tokenless
ANOLISA local marketplace — bundles the Token-Less plugin for Claude Code.
master-skill
Buddhist Master AI Skills — 14 historical masters across 汉传/藏传/南传 plus 3 teaching meta-skills (compare / debate / curriculum), with source-cited teachings.
inkbox
Plugin marketplace listing 1 plugin: inkbox.
peephole
Plugin marketplace listing 1 plugin: peephole.
agent-harness
Portable AI agent harness — curated review/build/test agents, secret-hardening + worktree + plan-gate hooks, and spec/supervise/wrap/verify-completion skills. Install once, use in every project. AI-agnostic core (Claude Code / Codex / Gemini).
telescope
Bounded public agent-surface evidence mapping.