target-auditlisted

<!-- Generated by agnostic-ai. Do not edit this file directly; edit specs under .agnostic-ai/ and run `agnostic-ai sync`. --> # target-audit Answers one question: **do these tools still read what agnostic-ai emits?** Adapters encode a snapshot of every vendor's config format. Those vendors ship weekly. Drift is silent. A moved skills directory keeps syncing cleanly, keeps `sync --check` green, and stops reaching the tool. This skill finds that drift on a schedule instead of via a user bug report. ## Arguments - no args: audit every registered target **and file an issue per confirmed finding**. Filing is the default, not an opt-in. - `claude zed kilo`: audit only those - `--no-file-issues`: stop at the report. Use it for a scratch run you do not intend to act on. - `--fix`: file issues, then open a PR per fix bucket. Never merges. **Why filing is the default.** It used to be opt-in, and two consecutive runs proved that wrong. The 2026-08-19 run found 52 findings and filed none. The 2026-08-27 run found 54 and filed none until a human asked, by which point it was re-verifying the previous run's backlog instead of auditing. The report lands in gitignored `local/`, so a run that does not file leaves **nothing** behind: no tracked work, no dedupe set for the next run, and a fresh re-derivation of the same findings a week later. A report nobody can act on is not a cheaper audit, it is a wasted one. ## Phase 1: Scope ```bash scripts/target-facts.sh --list