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.
npx skills add ANcpLua/ancplua-claude-plugins --skill charongit clone --depth 1 https://github.com/ANcpLua/ancplua-claude-pluginsWrote 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/skills/ancplua/ancplua-claude-plugins/charon)<a href="https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/charon"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/charon/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/skills/ancplua/ancplua-claude-plugins/charon"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/charon.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00134 | $0.03341 |
| Opus 5 | $0.00067 | $0.01670 |
| Sonnet 5 | $0.00027 | $0.00668 |
| Haiku 4.5 | $0.00013 | $0.00334 |
Grade B, and why
charon scanned grade B with 1 finding 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 9d 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
(2) Never tell the user to "just wait" — either you are doing something, or you name the How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Charon — the PR ferry
You carry one PR across the river to merge. Each turn is one iteration:
GROUND → CLASSIFY → DISPATCH (one handler) → SET STATUS → END TURN
You do not loop by hand. The Stop hook re-enters you while work is actionable, lets you rest while CI runs, and finishes when the PR is merged / closed / needs-you. Your only jobs each iteration: gather truth, do one honest unit of work, and record an honest status.
Three laws. (1) Never gh pr checks --watch; never poll or sleep in a tight loop.
(2) Never tell the user to "just wait" — either you are doing something, or you name the
one thing only they can do. (3) Never apply a reviewer suggestion blindly — verify it
against the real code, and verify any version it names is current, before touching a file.
1. GROUND — establish the ferry (if needed), then one live snapshot
Rebuild every decision from current state. Cached branch labels, old chat summaries, and
stale AGENTS.md/CLAUDE.md conclusions are not authority. This is also how you
avoid the "multiple options / half-finished PR / preexisting implementation" confusion:
read what is true now, not what something claims.
Establish the ferry per references/establish.md — read it once, on
first entry only (and again only when an explicit PR redirects an existing ferry). It is the single
"establish once" both solo entry points share, and it now also handles the fleet-lookout skip (a
charon:lookout works its one assigned PR directly and writes no solo state file) and explicit-PR
precedence (a PR the user names beats a pre-existing .claude/charon.local.md). Otherwise: if the
state file already exists, read pr: from it; if not, resolve and write it there. Then take ONE live
snapshot:
PR=<number>
gh pr view "$PR" --json number,title,state,isDraft,headRefName,baseRefName,headRefOid,baseRefOid,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup,reviews,comments,autoMergeRequest,url
gh pr checks "$PR" # ONE snapshot — never --watch
git fetch --all --prune --tags --quiet
git status --short --branch
What ships with it
1 file beside SKILL.md 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.
- 9d ago First seen · 236 lines · 134 tokens per session scan B e0d8e9739aa2
charon is a skill published in the GitHub repository ANcpLua/ancplua-claude-plugins (6 stars, last pushed 22d ago), licensed MIT. It adds 134 tokens to every session and 3,341 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
bisect
Bisect regressions or broken builds in the Chromium repository using deterministic binary search, checking out midpoint commits, syncing dependencies with gclient sync, compiling the target with autoninja, and querying the user for test results until the culprit commit is isolated.
mantis-critic
Assesses the production viability of findings, filtering out debug-only features and assertion traps. Use when findings have been validated and you need to confirm they are triggerable in production release builds (with assertions disabled). Don't use for writing reproduction scripts or patches.
hotpath_bump
Bump the hotpath version number across the workspace and related files. Updates crate versions in Cargo.toml files (exact patch version) and version references in the backend middleware, hotpathinit skill, and README (major.minor only). Use when the user wants to bump, bump the version, or release a new hotpath…
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.