# AI use cases for ECC (affaan-m/ECC)

Repo: [affaan-m/ECC](https://github.com/affaan-m/ECC) | Use cases: 4 | Page: https://dedupedai.com/use-cases/affaan-m-ecc/

ECC is an MIT-licensed agent harness of skills, agents, hooks, memory, and AgentShield security scanning that runs with Claude Code, Codex, and other coding agents.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Install ECC as a Claude Code plugin in one guided run: https://dedupedai.com/use-cases/affaan-m-ecc/install-ecc-claude-code-plugin/
- Preview, then install ECC into Claude Code and Codex together: https://dedupedai.com/use-cases/affaan-m-ecc/configure-claude-and-codex-together/
- Scan agent prompts, hooks, and permissions for security issues: https://dedupedai.com/use-cases/affaan-m-ecc/scan-agent-config-with-agentshield/
- Find the right ECC skill for a task before starting work: https://dedupedai.com/use-cases/affaan-m-ecc/find-the-right-ecc-skill-for-a-task/

## How to install ECC as a Claude Code plugin in one guided run with ECC

Repo: [affaan-m/ECC](https://github.com/affaan-m/ECC) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README

Get ECC's skills, agents, commands, and hooks into Claude Code without manual file copying.

**Who it is for:** A developer who uses Claude Code daily and wants the ECC agents and skills available in every session.

**The problem:** Setting up agents, skills, and hooks by hand is slow, and layering manual and plugin installs can duplicate them.

**The outcome:** The ecc@ecc plugin is enabled in Claude Code, and the guided setup handles later updates and scope changes.

### Steps

1. Install Node.js 18 or newer, Git, and Claude Code, then confirm with `node --version`, `git --version`, and `claude --version`.
2. Run `npx ecc-universal@2.2.3 setup`.
3. Choose Global user scope and Standard hooks for a typical personal setup, then confirm.
4. Start a new Claude Code session and run `/plugin list` to check that ecc@ecc is enabled.

### Prompt to paste into your agent

```text
On this machine, install the ECC Claude Code plugin from github.com/affaan-m/ECC by running `npx ecc-universal@2.2.3 setup` with the scope <scope>. Report the output of `/plugin list` and confirm that ecc@ecc is enabled, without adding a manual Claude install.
```

### Caveat

Do not combine this with the native /plugin commands or a full manual Claude install, because that can duplicate skills, commands, and hooks.

Risk, remote script: The npx command runs package code from the ecc-universal npm release, so review the release source and registry integrity before you run it.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/affaan-m-ecc/install-ecc-claude-code-plugin/

## How to preview, then install ECC into Claude Code and Codex together with ECC

Repo: [affaan-m/ECC](https://github.com/affaan-m/ECC) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Use the multi-harness wizard to set up two coding agents in one reviewed flow.

**Who it is for:** A team lead whose engineers use both Claude Code and Codex and want the same ECC setup in each.

**The problem:** Configuring two coding agents separately means two sets of choices, and it is easy to end up with mismatched or duplicated installs.

**The outcome:** Claude Code and Codex are configured in one reviewed run, with a dry-run preview shown before any write.

### Steps

1. Preview the Codex path without writing: `npx ecc-universal@2.2.3 install --guided --harness codex --dry-run`.
2. Run `npx ecc-universal@2.2.3 install --guided` and select Claude Code and Codex.
3. Review each install channel and destination shown, then confirm the single final prompt.
4. For automation, pass explicit flags: `npx ecc-universal@2.2.3 install --guided --harness claude --harness codex --claude-scope local --claude-hooks standard --profile core --yes`. (inferred, check the README)

### Prompt to paste into your agent

```text
Using the ECC repo at github.com/affaan-m/ECC, preview a guided install for Claude Code and Codex with `npx ecc-universal@2.2.3 install --guided` and report the install channel and destination for each harness in <project-path>. Verify that the preview shows no writes before you confirm.
```

### Caveat

The README says Kimi Code hooks, model and provider settings, and authentication are not configured by the guided install, and other adapters are capability-limited.

Risk, remote script: The guided install runs package code from npm, so review the release source and registry integrity before you confirm.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/affaan-m-ecc/configure-claude-and-codex-together/

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

Repo: [affaan-m/ECC](https://github.com/affaan-m/ECC) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

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

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

**The problem:** Agent 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 outcome:** A scan report that lists findings across prompts, hooks, MCP config, permissions, secrets, and agent files.

### 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 to paste into your agent

```text
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.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/affaan-m-ecc/scan-agent-config-with-agentshield/

## How to find the right ECC skill for a task before starting work with ECC

Repo: [affaan-m/ECC](https://github.com/affaan-m/ECC) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Ask ECC which skill fits a request, such as security reviews, from its 311 skills.

**Who it is for:** A developer who has ECC installed but does not know which of its many skills or agents fits the current task.

**The problem:** A large skill library is hard to browse, so people either skip useful skills or pick the wrong one.

**The outcome:** A short suggestion of the ECC skills that match your request, targeted at the harness you use.

### Steps

1. Confirm ECC is installed by following the guided setup steps first.
2. Run `npx ecc-universal@2.2.3 consult "security reviews" --target claude` and replace the quoted text with your own request.
3. Read the suggested skills and pick the one that matches the task.
4. Start the task in Claude Code and ask the agent to use that skill by name.

### Prompt to paste into your agent

```text
Using the ECC package ecc-universal from github.com/affaan-m/ECC, run `npx ecc-universal@2.2.3 consult "<request>" --target claude` and return the top suggested skills with a one-line reason for each. Verify that each suggestion exists in the consult output before you use it.
```

### Caveat

The consult command depends on the ecc-universal 2.2 alias, so it is only available in that release line and not in older ECC installs.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/affaan-m-ecc/find-the-right-ecc-skill-for-a-task/
