Skip to content
Back to skills

Downshift Setup

DSecurity

Install or repair Downshift hooks for any harness (Claude Code, Cursor, Codex, Antigravity, KiroCrew). Use to install, set up, wire, fix or undo Downshift, or when subagents never change model. Dry-run first, write only after a yes.

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added November 17, 2026
ai-agentsgogit

Works with

  • claude code
  • cursor
  • mcp

Security analysis

D42/100
  • criticalPipes output to a shell interpreter
  • mediumUses curl or wget to download content
  • criticalDownloads and executes remote scripts — classic supply chain attack

Pro shows the line behind each finding and how to fix it

Scanned November 17, 2026

npx -y skills add tiagovilasboas/downshift-ai --skill downshift-setup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Downshift Setup?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Downshift Setup
[![Security: D — Skills Directory](https://www.skillsdirectory.com/api/skills/tiagovilasboas-downshift-setup-downshift-ai/badge)](https://www.skillsdirectory.com/skills/tiagovilasboas-downshift-setup-downshift-ai)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: downshift-setup
description: Install or repair Downshift hooks for any harness (Claude Code, Cursor, Codex, Antigravity, KiroCrew). Use to install, set up, wire, fix or undo Downshift, or when subagents never change model. Dry-run first, write only after a yes.
---

# Downshift setup

Assisted, never silent. Every write outside the repository is shown as a diff and
waits for the user's yes. Never read or print task prompts. This skill is for the
first day: once `downshift doctor` is clean, ignore it (a hand-copied install can
delete it; the plugin copy stays and costs one description line).

## 1. Binary

1. `downshift version`. If missing, or older than the latest release
   (`gh release view --repo tiagovilasboas/downshift-ai --json tagName` or the Releases page):
   `curl -fsSL https://raw.githubusercontent.com/tiagovilasboas/downshift-ai/main/install.sh | sh`
   (macOS / Linux) or the Releases page or `go install`; see `docs/guides/install.md`. Never
   skip this because hooks are wired: `setup` reports "up to date" for the config, not the
   binary. Then `which -a downshift`: the first one must be the new build. An older copy
   earlier on PATH (often `~/go/bin`) shadows it; replace or remove that copy, then recheck
   `downshift version`.
2. Claude Code only: the plugin (`/plugin marketplace add tiagovilasboas/downshift-ai`, then
   `/plugin install downshift@downshift`) wires the same hooks and the `/downshift:status`
   slash command without touching `~/.claude/settings.json`. Use one
   path, plugin or `setup`, not both: `setup` skips the hooks when it sees the plugin enabled,
   and `downshift doctor` warns when both are wired.

## 2. Hooks

1. `downshift setup --dry-run`: one diff per harness found. Show it. Explain the Claude Code
   extras it adds only for keys the user has not set: `"model": "opusplan"` (Opus plans,
   Sonnet executes), sessions starting in plan mode, Claude Code's built-in You should know mod
   (each check is a billed background request: say so), a statusline. `--no-session-policy`
   skips the first three. Name the other things the diff adds, each with its opt-out:
   the `downshift` MCP server in Claude Code and Codex (`--no-mcp`); the Downshift skills
   the plugin lacks (`downshift-audit`, `downshift-orchestrator`, `downshift-effort`,
   `downshift-squad`, `ponytail`); on Claude Code, the `downshift-agents` mod, a band above
   the prompt and a `/ds-agents` pane that only observe (`--no-mods`). Every harness with an instructions file (`~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md`, ...) gets a marked block with the agent triggers (`downshift full power`), so the squad is called at once. `downshift setup
   claude-code --dry-run` limits the run to one harness.
2. Only after a clear yes: `downshift setup --yes`. Backups are kept; `downshift setup --undo`
   restores the latest.
3. KiroCrew needs its wrapper script and is only reported by `setup`; follow the KiroCrew
   section of `docs/guides/install.md`. Grok is config, not a hook.

## 3. Check

1. `downshift doctor --json`: handle every `warn` or `fail` with its `fix`, asking before any
   config write. A `companion` row about Headroom is optional; see `docs/guides/companions.md`.
2. Session models: Claude Code infers them from the current model. Other harnesses need
   `downshift models discover` or `~/.downshift/session-models.json`
   (`docs/reference/session-models.md`).
3. Plan limits decide whether a rewrite is honored, not Downshift
   (`docs/reference/harness-matrix.md`). Say so when the plan is Free or legacy Cursor Pro.
4. Ask the user to open a **new** harness session, spawn a trivial subagent, and check
   `downshift session`, or in Claude Code `/downshift:status` (plugin) or `/downshift` (manual alias).
   The stderr line `downshift: TRIVIAL task → downshift to …`
   proves the hook fired; the matrix says whether it was applied.

Do not invent hook paths, matchers or catalog entries; everything above is in
`docs/guides/install.md` and `examples/`.

Downshift by Tiago Vilas Boas · https://github.com/tiagovilasboas/downshift-ai

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.