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/wei18/upkeep/upkeep-auditnpx skills add wei18/Upkeep --skill upkeep-auditgit clone --depth 1 https://github.com/wei18/UpkeepWhat 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.00040 | $0.00525 |
| Opus 5 | $0.00020 | $0.00262 |
| Sonnet 5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
upkeep-audit 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
Upkeep Local Audit
Run the full Upkeep audit pipeline (discovery → parallel reviewers → synthesis → HTML report) against a local repository. Output-only: the target repo is never modified.
Steps
- Ensure the Upkeep checkout at
~/.cache/upkeep:- Missing:
git clone --depth 1 https://github.com/wei18/upkeep ~/.cache/upkeep - Present:
git -C ~/.cache/upkeep pull --ff-only(if the pull fails — diverged or dirty checkout — delete~/.cache/upkeepand re-clone; it is disposable) - Then
(cd ~/.cache/upkeep && npm ci)after a fresh clone or whenever the pull changedpackage-lock.json(when unsure, run it — it is idempotent).
- Missing:
- Run the audit (takes several minutes; reviewers run as parallel
claude -psubprocesses — run it in the background and report progress):
Pass flags only when the user asked for them, with one exception: the report defaults to~/.cache/upkeep/scripts/local-audit.sh <target-path> [--model M] [--rubric-lang L] [--max-turns N] [--out FILE]./upkeep-report.htmlin the current working directory, so if the working directory is inside the target repo, pass--outpointing outside it (e.g.~/upkeep-report.html) — the audit must never write into the target repo. Other defaults match the CI inputs (claude-opus-4-8, rubricen,30turns);--rubric-langacceptsenorzh-TW. - Summarize: the script prints the report markdown at the end. Present the findings grouped by severity (high → medium → low), each with its file path and a one-line problem statement, then give the absolute path of the generated report file (
upkeep-report.htmlby default, or the--outpath). If any reviewers failed, name them.
Requirements (tell the user what is missing instead of failing silently)
claudeCLI installed and logged in (Claude Pro/Max subscription).- Node 20+, git.
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.
- 2d ago First seen · 27 lines · 40 tokens per session scan A f9679960072a
upkeep-audit is a skill published in the GitHub repository wei18/Upkeep (14 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 525 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.