DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to scan agent prompts, hooks, and permissions for security issues with ECC

Run AgentShield over an agent setup to check prompts, hooks, MCP config, permissions, and secrets.

Who it is forA security-minded developer who is about to share or publish an agent configuration and wants it checked first.

The problemAgent configuration files mix prompts, hooks, MCP settings, and permissions, and it is easy to leave a secret or an overly broad permission in place.

The outcomeA scan report that lists findings across prompts, hooks, MCP config, permissions, secrets, and agent files.

What you need first

  • Node.js 18 or newer
  • Git on PATH
  • Claude Code 2.1 or newer for plugin setup
  • Access to github.com and npm to fetch the official ECC packages

Steps

  1. Open a terminal in the project folder that holds your agent files.
  2. Run npx ecc-agentshield to start a scan of the current folder. (inferred, check the README)
  3. Read each finding and note the file it points to.
  4. Remove or rotate any exposed secret, and tighten any permission the report flags.
  5. Rerun the scan until the findings you accept are the only ones left.

Prompt for your agent

Using the ecc-agentshield package from the ECC project, scan <project-path> for issues in prompts, hooks, MCP config, permissions, secrets, and agent files. Return a list of findings with file paths and confirm that no secret values appear in your output.

Caveat. The README lists what AgentShield scans but does not say it fixes findings, so you still need to review and change the files yourself.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page