sync

A setup and update guide for keephive, a tool and its related components. It checks for the uv package manager, installs or updates keephive, and runs its setup process.

In plain words
What is it for?
Use it when installing, updating, or setting up keephive and checking its installed version.
Why use it?
It provides a repeatable way to prepare a machine or bring an existing keephive installation up to date. It stops early when a required package manager is missing.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/joryeugene/keephive/sync
Any agent
npx skills add joryeugene/keephive --skill sync
Clone the repo
git clone --depth 1 https://github.com/joryeugene/keephive

Made for: Claude Code, Codex.

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 598 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 3 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00056 $0.00598
Opus 5 $0.00028 $0.00299
Sonnet 5 $0.00011 $0.00120
Haiku 4.5 $0.00006 $0.00060

Measured 2d ago against content hash 6872ad358ed2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

sync scanned grade D with 3 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

> `curl -LsSf https://astral.sh/uv/install.sh | sh`

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

Read `~/.claude/settings.json` and check the `enabledPlugins` object for any key containing `claude-stack`.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

> `curl -LsSf https://astral.sh/uv/install.sh | sh`
skills/sync/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

keephive Sync

Install keephive from scratch or bring an existing installation up to date. This skill walks through each step, verifying as it goes.

Step 1: Check for uv

Run which uv to confirm the package manager is available.

If uv is not found, tell the user:

uv is required but not installed. Install it with: curl -LsSf https://astral.sh/uv/install.sh | sh

Then re-run this sync.

Stop here if uv is missing. Do not proceed.

Step 2: Install or update keephive

Check if keephive is already installed:

which keephive

If installed, update to the latest version:

uv tool install --force keephive

If not installed, install fresh:

uv tool install keephive

After install, verify:

keephive --version

Print the installed version.

Step 3: Run setup

Run the full setup to register hooks, MCP server, seed content, and initialize KingBee:

keephive setup --yes

This is idempotent. Running it on an already-configured machine updates anything that drifted without destroying existing data.

Step 4: Offer claude-stack companion

Read ~/.claude/settings.json and check the enabledPlugins object for any key containing claude-stack.

If claude-stack is already installed, print:

claude-stack is already installed. No action needed.

If claude-stack is NOT installed, ask the user:

claude-stack provides engineering discipline for Claude Code: TDD, debugging protocols, spec-writing, verification workflows, and enforcement hooks. keephive handles memory. claude-stack handles methodology. They pair directly.

Install claude-stack? (This requires user confirmation.)

Only proceed if the user explicitly says yes. If yes:

claude plugin install joryeugene/claude-stack

If the user declines, acknowledge and move on. Do not ask again.

Step 5: Summary

Print what was done:

  • keephive version installed/updated
  • Hooks registered (count)
  • MCP server status
  • claude-stack status (installed / declined / already present)
  • Next steps: hive s to check status, hive doctor to verify health

Read the full file on GitHub · 93 lines

Changes

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.

  1. 2d ago First seen · 93 lines · 56 tokens per session scan D 6872ad358ed2

Subscribe to this mod's changes

sync is a skill published in the GitHub repository joryeugene/keephive (1 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 598 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 3 findings (downloads and executes remote code, reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens