← ClaudeAtlas

agent-config-reviewlisted

Review a coding agent's configuration for access broader than the work needs and give a verdict — SAFE AS CONFIGURED, TIGHTEN BEFORE USE or DO NOT USE — reading what actually wins across every scope (Claude Code user, project, local and managed settings; permission allow/deny/ask lists, defaultMode, sandbox, hooks, plugins, env; .mcp.json; subagent tool lists; Codex sandbox_mode and approval_policy and the profile in use; Cursor and Copilot agent settings), with each finding's file and line, what it lets happen in plain words, and the exact replacement config. Use when the user asks "is this Claude Code / Codex / Cursor setup safe", "review our .claude/settings.json", "audit our agent permissions", "is Bash(npm:*) OK in the allow list", "check this repo's agent config before we open it", or wants an agent's permissions tightened before use.
sananthanarayan/skilldrop · ★ 2 · AI & Automation · score 65
Install: claude install-skill sananthanarayan/skilldrop
# agent-config-review Reads the configuration a coding agent will actually run with and says whether it is safe to use as it stands. The files lie by omission: the effective permission is what every scope adds up to, an allow entry means what the command can do rather than what it is called, and the settings that run shell without asking (hooks, status lines, MCP servers) sit outside the sandbox. The output is a verdict, the findings worst first, and the config that replaces each. It reviews an existing setup. Choosing which MCP servers a workflow should connect is `mcp-pairing`; attacking an agent's design for data-exfiltration paths is `agent-threat-model`. ## How to respond **Four rules come before the steps and outrank them:** - **Answer what was asked, first.** Open with the answer, the decision or the artifact, in plain words. Scores, matrices, frameworks and tags come after it, and anything that doesn't change the answer is cut. - **Use only what you were given.** Don't add facts, names, numbers, incidents, history, steps or sections the input doesn't contain. What you need and don't have is left out of the artifact and listed once at the end under "To confirm". - **Deliver from what you have.** When the request gives you something to work on, state your assumptions in a line and produce the result. When it gives you nothing to work on, ask for it in one or two plain sentences and say what you will do once you have it. - **Write for someone who has never heard of