القائمة
Scan your tool configuration for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks instruction files, settings, MCP servers, hooks, and agent definitions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | security-scan |
| description | Scan your tool configuration for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks instruction files, settings, MCP servers, hooks, and agent definitions. |
Audit your tool configuration for security issues using AgentShield.
| File | Checks |
|---|---|
Instruction file (AGENTS.md, CLAUDE.md, equivalent) | Hardcoded secrets, auto-run instructions, prompt injection patterns |
| Tool settings/config | Overly permissive allow lists, missing deny lists, dangerous bypass flags |
| MCP config | Risky MCP servers, hardcoded env secrets, npx supply chain risks |
| Hooks | Command injection via interpolation, data exfiltration, silent error suppression |
| Agent definitions | Unrestricted tool access, prompt injection surface, missing model specs |
AgentShield must be installed. Check and install if needed:
# Check if installed
npx MDT-agentshield --version
# Install globally (recommended)
npm install -g MDT-agentshield
# Or run directly via npx (no install needed)
npx MDT-agentshield scan .
Run against the current tool or project config directory:
# Scan current project
npx MDT-agentshield scan
# Scan a specific path
npx MDT-agentshield scan --path /path/to/tool-config
# Scan with minimum severity filter
npx MDT-agentshield scan --min-severity medium
# Terminal output (default) — colored report with grade
npx MDT-agentshield scan
# JSON — for CI/CD integration
npx MDT-agentshield scan --format json
# Markdown — for documentation
npx MDT-agentshield scan --format markdown
# HTML — self-contained dark-theme report
npx MDT-agentshield scan --format html > security-report.html
Apply safe fixes automatically (only fixes marked as auto-fixable):
npx MDT-agentshield scan --fix
This will:
Run the adversarial three-agent pipeline for deeper analysis:
# Requires ANTHROPIC_API_KEY
export ANTHROPIC_API_KEY=your-key
npx MDT-agentshield scan --opus --stream
This runs:
Scaffold a new secure .claude/ configuration from scratch:
npx MDT-agentshield init
Creates:
settings.json with scoped permissions and deny listCLAUDE.md with security best practicesmcp.json placeholderAdd to your CI pipeline:
- uses: affaan-m/agentshield@v1
with:
path: '.'
min-severity: 'medium'
fail-on-findings: true
| Grade | Score | Meaning |
|---|---|---|
| A | 90-100 | Secure configuration |
| B | 75-89 | Minor issues |
| C | 60-74 | Needs attention |
| D | 40-59 | Significant risks |
| F | 0-39 | Critical vulnerabilities |
Bash(*) in the allow list (unrestricted shell access)${file} interpolation2>/dev/null, || true)npx -y auto-install in MCP server configsHow to use the Serena MCP server for token-efficient code navigation, symbol analysis, and targeted editing. Use this skill whenever Serena tools are available (mcp__serena__* tools appear in your tool list), when exploring unfamiliar codebases, before editing any file larger than ~100 lines, when finding all callers of a function, or when you need to understand a module without reading it whole. ALWAYS prefer Serena's symbolic tools over raw Read calls for TypeScript, JavaScript, Python, or any language with LSP support — it is almost always faster and cheaper.
Use context-mode tools (ctx_execute, ctx_execute_file) instead of Bash/cat when processing large outputs. Triggers: "analyze logs", "summarize output", "process data", "parse JSON", "filter results", "extract errors", "check build output", "analyze dependencies", "process API response", "large file analysis", "page snapshot", "browser snapshot", "DOM structure", "inspect page", "accessibility tree", "Playwright snapshot", "run tests", "test output", "coverage report", "git log", "recent commits", "diff between branches", "list containers", "pod status", "disk usage", "fetch docs", "API reference", "index documentation", "call API", "check response", "query results", "find TODOs", "count lines", "codebase statistics", "security audit", "outdated packages", "dependency tree", "cloud resources", "CI/CD output". Also triggers on ANY MCP tool output that may exceed 20 lines.
Instinct-based learning system for Codex. Manual-first: explicit capture and analysis baseline, with optional background observer.
Keep repository documentation current, accurate, well-placed, and easy to follow for both humans and LLMs. Use when auditing doc drift, correcting stale claims, deciding where docs belong, or validating documentation quality before a commit.
Instinct-based learning system that adapts to the environment: hooks-passive observation for Claude/Cursor, explicit capture for hook-free tools. Single unified surface for all tools.
Keep repository documentation current, accurate, well-placed, and easy to follow for both humans and LLMs. Use when auditing doc drift, correcting stale claims, deciding where docs belong, or validating documentation quality before a commit.