agentleFS
Sign inStart free
tiagovilasboastiagovilasboas/downshift-ai/skills/downshift-audit/SKILL.md

downshift-audit

Skill4 starsChanged 9 days agoApache-2.0View on GitHub

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 its hooks are wired, or where subagent tokens go; the fixed-context measurement is part of that audit, not a standalone trigger.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read-only. Never edit settings, hooks or context files without the user's approval.

    line 8
  2. Very specific:

    Add the skill descriptions (the description: line of each SKILL.md).

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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):

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.

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free