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 agentmods add skills/melodic-software/claude-code-plugins/recheck-against-upstreamnpx skills add melodic-software/claude-code-plugins --skill recheck-against-upstreamgit clone --depth 1 https://github.com/melodic-software/claude-code-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/melodic-software/claude-code-plugins/recheck-against-upstream)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/recheck-against-upstream"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/recheck-against-upstream.svg" alt="Measured on agentmods" 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 | $0.00114 | $0.01378 |
| Opus 5 | $0.00057 | $0.00689 |
| Sonnet 5 | $0.00023 | $0.00276 |
| Haiku 4.5 | $0.00011 | $0.00138 |
Grade A, and why
recheck-against-upstream 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recheck against upstream
A drift corrector for the discipline that existing state does not vouch for
itself. The method, re-anchor, audit the work in flight, correct forward,
report, and the tone that firing this is not an accusation, lives in
${CLAUDE_PLUGIN_ROOT}/context/re-anchor-audit-correct.md.
Read it; this file adds only what is specific to upstream-conformance
discipline.
The discipline this re-anchors
Existing state, a config file, a code path, a runbook, an infra
definition, is evidence of what is, never proof that it matches the
upstream it depends on. Upstream ships new defaults, renames flags,
deprecates APIs, and obsoletes yesterday's workaround; the state that was
correct when written silently rots. Resolve the source of truth per the
method doc's ladder: if the consuming project states an
upstream-conformance rule in its own CLAUDE.md / .claude/rules/,
re-anchor THAT. Otherwise re-anchor this portable baseline:
- Present state is not self-justifying. "It's already configured this way" and "the code does X" describe the state; neither shows it still matches upstream. Conformance is a claim to verify, not to assume.
- Compare against the CURRENT official upstream, fetched now. Re-read the vendor's live documentation for the surface in play this session, never training-data recall of it, never a stale in-repo summary of it.
- Resolve the applicable upstream version first. When the repo pins a supported major/minor, compare against the docs for THAT version. The latest docs can legitimately prescribe APIs and defaults the pin does not have. Divergence between the pinned line and latest is its own finding (upgrade candidate or deliberate hold), never a false gap against the pin.
- Unverified conformance is not "clean". A surface you did not compare is unaudited, not passing. Report what was compared and what was skipped; do not launder the unchecked into a green result.
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.
- yesterday First seen · 105 lines · 114 tokens per session scan A 7cde1be8b7bd
recheck-against-upstream is a skill published in the GitHub repository melodic-software/claude-code-plugins (15 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 1,378 once invoked, about $0.0006 per session on Opus 5. 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-09-03.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
build-priority-queue
For ordered processing: A search, Dijkstra, event simulation, task scheduling. Efficient min/max extraction with heap-based queue.
catch-expected-errors
For iteration with errors: catch exceptions during exploration, skip invalid cases, continue to next attempt.
compose-small-helpers
For complex behavior: build from tiny functions, chain transformations, make code read like a pipeline of operations.
count-combinations
For probability and counting: permutations, combinations, sample spaces, Monte Carlo simulation, brute-force enumeration, card/dice problems.