npx steering.sh
Package manager for AI agent steering files
Distribute consistent AI context —standards, architecture, conventions— across your whole team from a Git repo. The same workflow as npx skills, but for steering files — Kiro, Cursor, Claude Code, Copilot, and more.
Skills run on demand.
Steering is always on.
Complementary layers, not alternatives. Skills are capabilities your agent reaches for. Steering is the context it can’t afford to forget — the layer steering.sh distributes across your team.
Skills
pullagent → skill · on demand
- Loaded only when the agent decides it's relevant.
- Best for procedures, tools, and one-off workflows.
- Free when idle — nothing in context until it fires.
Steering
pushsteering → agent · every turn
- Always in context, or scoped to a path.
- Best for standards, guardrails, and project truth.
- Applies deterministically — even when the model would forget.
A skill only fires when the model thinks to reach for it. A steering file applies every time — which is why the context that must never be forgotten belongs in one, versioned in Git and distributed with a single command.
Why steering
One command, zero setup
npx steering.sh add owner/repo writes steering files straight into each agent's native location. No cloning, no manual copying.
Public and private repos
Uses GITHUB_TOKEN, GH_TOKEN or gh auth token. Built to distribute internal context across a whole team.
SHA-based updates
steering check compares the blob SHA against GitHub, and steering update pulls only what changed.
Conflict-free lock file
The local lock is minimal (no hashes or timestamps) to keep git merge conflicts to a minimum.