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/wei18/UpkeepWrote 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/wei18/upkeep/upkeep-audit)<a href="https://agentmods.dev/plugins/wei18/upkeep/upkeep-audit"><img src="https://agentmods.dev/badge/plugins/wei18/upkeep/upkeep-audit/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/wei18/upkeep/upkeep-audit"><img src="https://agentmods.dev/badge/plugins/wei18/upkeep/upkeep-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
upkeep 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 2mo 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": "upkeep",
"description": "Run the Upkeep repo audit locally against any repository path — output-only drift report with evidence and severity.",
"version": "2.1.1",
"author": {
"name": "Wei18"
},
"homepage": "https://github.com/wei18/upkeep",
"repository": "https://github.com/wei18/upkeep"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 40 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.
- 2mo ago First seen · 11 lines scan A 69820b22c0e2
upkeep is a plugin published in the GitHub repository wei18/Upkeep (16 stars, last pushed 4d 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-30.
Other plugins, from other repositories
opencode-power-pack
Fifty-five workflows for Claude Code, Codex, OpenCode 1 and 2, and Pi.
quality-assurance-suite
Find gaps that could break a release, mislead a maintainer, or make a passing test meaningless.
atc-skills
A 12-skill depth pack for ATC — the ACM SIGOPS Annual Technical Conference (formerly the USENIX Annual Technical Conference): USENIX's broad practical-systems venue now under SIGOPS, the new two-round extended-abstract HotCRP review, double-blind reviewing, the Deployed Systems / experience-paper track, USENIX-lineage.
aspark
An agile AI product team for Claude Code — Specify, Plan, Act, Review, Keep. A Product Owner, Designer, Engineering Manager, Reviewer, QA Tester and Release Manager work your feature through a gated delivery loop.
diffctx
Selects the minimum code an LLM needs to review a git diff.
forgedock
Autonomous AI development pipeline that uses GitHub as a structured knowledge graph for Claude Code agents. Adds /work-on, /review-pr, /quality-gate, /orchestrate, and 20+ pipeline commands.