Skip to content
Back to skills

Downshift Audit

ASecurity

Read-only audit of a Downshift install and its fixed agent context. Use when the user names Downshift and asks why it does not rewrite models, whether hooks are wired, or where subagent tokens go.

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

Works with

  • claude code
  • cursor

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 17, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Downshift Audit?

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

Security grade badge for Downshift Audit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tiagovilasboas-downshift-audit-downshift-ai/badge)](https://www.skillsdirectory.com/skills/tiagovilasboas-downshift-audit-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-audit
description: Read-only audit of a Downshift install and its fixed agent context. Use when the user names Downshift and asks why it does not rewrite models, whether hooks are wired, or where subagent tokens go.
---

# Downshift audit

Read-only. Never edit settings, hooks or context files without the user's approval. Never read or print task prompts. Never promise a savings percentage: Downshift reports estimated savings, not billed cost.

## 1. Is it running?

1. `downshift doctor --json`: a checklist (`ok`/`warn`/`fail`, each with a `fix`). It covers the binary vs the hook command per harness, hooks wired, both state dirs, the session-model source, the last hook event, and a `rewrite honored` row that is inferred honor only (later same-session spawn correlation, not the child's observed model; `docs/guides/daily-truth.md`). Observed honor by harness: `docs/reference/harness-matrix.md` (Claude Code: PostToolUse `resolved`). Report the failed checks first.
2. Hook wiring: find where the user's harness keeps its hooks (`docs/guides/install.md` has one section per harness: Claude Code, Cursor, Codex, Antigravity, KiroCrew; Grok uses config, not a hook) and show only the hooks block. Expect a pre-spawn hook that runs `downshift <harness>`. Optional post-spawn hooks add honor and usage evidence where the harness supports them (`docs/reference/harness-matrix.md`).
3. Session models: Claude Code infers them from the current model when no list exists; other harnesses need a hook list, `downshift models discover` or `~/.downshift/session-models.json` (least to most capable). Missing hooks are fixed by `downshift setup --dry-run` then, with the user's approval, `downshift setup`.

## 2. What did it do?

- `downshift stats --days=7`: decisions and estimated savings. `--export` gives a prompt-free summary.
- `downshift quota status --harness <harness>`: only when quota evidence is in use.
- `downshift doctor` also lists model-override variables that are set (for any harness that declares one).
- Project floor: if `.downshift/policy.json` exists in the project, read it; an invalid file is ignored (fail-open), so validate its tiers and risk names by eye.
- `downshift session --why`: why each spawn of this session got its model.

## 3. Fixed context cost

Measure what loads every session. List the files the user's harness loads automatically (the paths below cover the common ones; skip what does not exist):

```bash
wc -c CLAUDE.md AGENTS.md GEMINI.md .claude/rules/* .cursor/rules/* .kiro/steering/* \
  ~/.claude/CLAUDE.md ~/.codex/AGENTS.md 2>/dev/null | sort -rn
```

Add the skill descriptions (the `description:` line of each `SKILL.md`). Estimate tokens as bytes / 4 and say it is an estimate. Rules added by portable compression skills (for example `headroom-skill` in `CLAUDE.md` or `AGENTS.md`) count here too.

Companion compressor: if `command -v headroom` finds a binary, report it and whether `downshift context status` records it (`Companion:` line). With a companion active, savings in `downshift stats` are routing only; compression numbers come from the companion's own counters. Details: `docs/guides/companions.md`. For each large always-loaded file, ask whether it applies to every project. Content for one domain belongs in a manual or file-matched rule.

## 4. Report

Table: finding | evidence (command and the line you read) | suggested fix | confidence (observed, inferred, unverified). Top three findings first. Mark anything you could not run as unverified.

Symptom-to-cause hints: [references/interpretation.md](references/interpretation.md).

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

Files in this skill

  • SKILL.md3.6 KB
  • references/interpretation.md1.6 KB

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.