How does a file in Downloads become a lasting change?
Found an instruction file you did not write? Paste it into the free AGENTS.md checker to see what it tells your agent to load and allow.
A locked-down agent can still ship an app that breaks at launch. Run what it built through the free vibe coding production checklist: 50 checks for auth, payments, data integrity and recovery.
Review settings.json before the next agent session. Keep sandbox and approval controls enabled.
Prefer an agent-driven review? Use the free coding-agent security-check prompt. That prompt asks your agent to review the machine; this script runs fixed checks without asking a model.
What will it look at?
Open a check to see its paths, keys and severity rules. These are review heuristics. A familiar server name or a recent timestamp needs context.
Default folders: Downloads, Desktop and temporary directories, including the configured XDG download folder. Add a repository with --scan PATH. Symlinks and credential files are skipped. Limits: depth 8, 50,000 files per tree and 2 MiB per file; incomplete coverage exits 2. Read checks.json.
Planted files in. Findings out.
17 / 17 planted artifact categories detected
The inert fixture recreates the instruction files, agent config changes and package indicators. Commands are replaced with true; the package directory contains a dummy manifest.
33 tests passed. The clean fixture with its reviewed baseline produced 0 findings, including 0 high findings.
The test suite also checks redaction, read-only behavior, backups and symlink handling. Fixture results demonstrate these checks, not detection rates on real attacks.
[high] instruction: ~/Downloads/CLAUDE.md
Instruction/config in an untrusted scan folder; L1: ANTHROPIC_BASE_URL … settings.json [other content withheld]
[high] instruction: ~/Downloads/AGENTS.md
Instruction/config in an untrusted scan folder; L2: config.toml … mcp_servers [other content withheld]; L3: npm install [other content withheld]
[high] ioc-function-color: ~/Downloads/project/package-lock.json
function-color package name found
[medium] instruction: ~/Downloads/project/.mcp.json
Instruction/config in an untrusted scan folder
[high] ioc-function-color: ~/Downloads/project/node_modules/function-color/package.json
node_modules/function-color package directory found
[medium] instruction: ~/Downloads/project/.claude/settings.local.json
Instruction/config in an untrusted scan folder
Actual fixture output excerpt. Home paths normalized to ~. Evidence shows matching source fragments with line numbers; other content is withheld.
Paste this into your agent
Give it the public file index before discussing a local review. Keep your configuration on your machine.
Fetch https://lab.anonyfox.com/coding-agent-security/index.md and https://lab.anonyfox.com/coding-agent-security/checks.json; explain the local checks and help me review the script before I run it.
The scan is free. Keep the response routine.
Use the checklist to review what you found. Add the team files when someone needs to own approvals, onboarding and the next review.
No VAT is charged under § 19 UStG (German small business regulation).
Before you run it
Does this send my configuration to an AI model?
The audit runs locally with Python’s standard library. It reads files and runs fixed read-only listings. It makes no model requests or network calls. Read the downloaded file before running it.
Does a clean result mean my machine is safe?
Exit 0 means these checks found nothing within their scan scope. It is not a malware clearance. Symlinks and credential files are skipped; depth, file-count and size limits report coverage errors. Exit 2 means a check could not complete.
Why does it flag my company proxy or MCP server?
A configured integration can be legitimate. Severity is a review heuristic. Confirm the destination and full command with the owner, then approve the reviewed host or exact server definition in a baseline. Risky launch commands stay flagged.
Will it change or delete anything?
The default scan writes nothing. --write-baseline FILE explicitly writes an allowlist. --fix asks before each supported change, unless you supply --yes. It moves stray instruction files into quarantine and backs up supported config edits. Persistence and npm cleanup stay manual.
Can I run it in a container instead?
Run the audit on the machine and account whose agent settings you want to inspect. A container normally sees its own home and files. Pass active repositories with --scan PATH. The script does not inspect remote agent hosts from your laptop.
What does it need, and does it support Windows?
Python 3.8 or newer on macOS or Linux, including WSL. Native Windows is not covered yet. Python 3.11 or newer supports full TOML parsing; older versions report unsupported syntax through the conservative fallback.
How is this different from the free security-check prompt?
The free prompt asks your agent to review the machine. This script performs fixed local checks without consulting a model. The paid kits add the response checklist and, for teams, editable working rules and rollout files.
What arrives after payment?
A ZIP attachment arrives by email within 24 hours. Solo contains the script and an 8-page checklist in A4 and US Letter PDF plus Markdown. Team adds policy, rollout and onboarding files in PDF, Markdown and Word, plus a baseline template. Team covers one company and all its staff.