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 ANcpLua/ancplua-claude-pluginsnpx agentmods add plugins/ancplua/ancplua-claude-plugins/charongit clone --depth 1 https://github.com/ANcpLua/ancplua-claude-pluginsGrade A, and why
charon 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 2d 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "charon",
"version": "0.3.3",
"description": "Ferries a GitHub PR to merge without waiting forever: an honest snapshot-not-block loop that fixes CI, repairs conflicts, version-checks reviewer suggestions, and never says 'just wait'.",
"author": {
"name": "ANcpLua",
"url": "https://github.com/ANcpLua"
},
"repository": "https://github.com/ANcpLua/ancplua-claude-plugins",
"license": "MIT",
"keywords": [
"pull-request",
"github",
"merge",
"ci",
"code-review",
"ferryman",
"babysit",
"loop",
"stop-hook",
"schedulewakeup",
"resume",
"honest-status",
"merge-conflict",
"version-verification",
"multi-agent",
"teams-api",
"propose-and-pause",
"recovery-ref"
]
}
What it installs
The manifest is a name and a version. 1 skill, 1 command, 2 agents travel with it, and installing the plugin installs all of them — 377 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2d ago First seen · 33 lines scan A 072ff15492fd
charon is a plugin published in the GitHub repository ANcpLua/ancplua-claude-plugins (5 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
nyann
Project governance for Claude Code. Bootstrap and maintain git workflow, hooks, commits, releases, CI, docs, and repo health.
org-management
GitHub organisation management including CI health, dependency audits, issue triage, maintenance, orchestration, releases, standards, and repo monitoring.
oss-skills
18 skills for open-source development: bootstrapping repos, API design, testing, CI, releases, supply-chain security, docs, triage, contributor experience, launch, and governance.
release-please-monorepo
Set up automated semantic versioning, changelogs, and per-package publishing in a pnpm/Turbo monorepo using googleapis/release-please-action v4.
npm-oidc-publish
Publish an npm package from GitHub Actions via OIDC trusted publishing — no NPMTOKEN, no OTP in CI.
claude-plugin-repo-ci-release
Wire up CI validation and automatic release-cutting for a Claude Code plugin or marketplace repo (one with a .claude-plugin/marketplace.json and plugins/). Adds two GitHub Actions — a structure validator on every PR/push, and a release-on-version-bump job that cuts a GitHub Release whenever VERSION changes — plus the.