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/yanfeid/claude-amberWrote 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/yanfeid/claude-amber/claude-amber)<a href="https://agentmods.dev/plugins/yanfeid/claude-amber/claude-amber"><img src="https://agentmods.dev/badge/plugins/yanfeid/claude-amber/claude-amber/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/yanfeid/claude-amber/claude-amber"><img src="https://agentmods.dev/badge/plugins/yanfeid/claude-amber/claude-amber.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
amber 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": "amber",
"description": "Zero-dependency context survival kit for Claude Code. Auto-checkpoints your session state to plain Markdown before compaction, restores it after — plus focus skills that keep Claude lean and on-task. No database, no background process, no AI compression. Just files you can read.",
"version": "0.1.0",
"author": {
"name": "yanfei",
"email": "[email protected]"
},
"homepage": "https://github.com/yanfeid/claude-amber",
"repository": "https://github.com/yanfeid/claude-amber",
"license": "MIT",
"keywords": [
"claude-code",
"context",
"compaction",
"memory",
"hooks",
"skills",
"context-engineering"
]
}
What it installs
The manifest is a name and a version. 4 skills, 3 hooks travel with it, and installing the plugin installs all of them — 244 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 · 22 lines scan A 87b951516b9d
amber is a plugin published in the GitHub repository yanfeid/claude-amber (2 stars, last pushed 4mo 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
handoff
Portable project memory + development workflow for coding agents: auto-loads STATUS+RULES each session, enforces folder-level CONTEXT.md on edit, nudges durable state updates at turn end, scaffolds the system into any repo via guided discovery, and ships a tiered 6-phase workflow skill set covering every phase (brief.
axme-code
(Alpha) Persistent memory, architectural decisions, and safety guardrails for Claude Code. Your agent starts every session with full project context — stack, decisions, patterns, safety rules, and a handoff from the previous session.
wire-memory
Persistent memory for AI agents. Connect to a Wire container to remember decisions, patterns, and context across sessions.
total-agent-memory
Persistent local memory for Claude Code — temporal knowledge graph, procedural memory, AST codebase ingest, cross-project analogy. Installs the MCP server, the memory-protocol skill and the capture hooks in one step.
engram
Durable, local-first graph memory for AI coding assistants: decisions with reasons, gotchas, conflicts — inspectable and editable in a graph pane.
atomicmemory
Persistent semantic memory for Claude Code — user preferences, project context, prior decisions, and codebase facts that survive across sessions.