skill/SKILL.md
Security auditing tool for AI development workflows, rules, skills, and MCPs.
npx skillsauth add ai-coding-shield/ai-coding-shield ai-coding-shieldInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill allows you to use ai-coding-shield to audit your AI development artifacts for security risks. It helps identify potential threats in workflows, MCP configurations, skills, and other agentic components.
Use this skill when you need to:
.github/workflows or other CI/CD scripts for security vulnerabilities.First, ensure the tool is installed by running the installation script provided in this skill:
./skill/scripts/install.sh
Once installed, you can use the ai-coding-shield CLI to perform various security tasks.
To audit the current directory or a specific path (e.g., .agent/):
ai-coding-shield audit .
Or for a specific folder:
ai-coding-shield audit .agent/
To see the catalog of threats that the tool can detect:
ai-coding-shield list
To understand a specific threat ID returned in a report:
ai-coding-shield info CMD_001
You can integrate ai-coding-shield into your GitHub Actions pipeline to automatically scan for risks on every push.
[!IMPORTANT] User Confirmation Required: Before adding this to a pipeline, you must explicitly confirm with the user that they want to enable automated security scanning in their CI/CD process.
If approved, you can add a step like this to your workflow file (e.g., .github/workflows/security.yml):
- name: AI Coding Shield Audit
uses: AI-Coding-Shield/ai-coding-shield@v1
with:
path: .
fail-on: high
development
A safe skill that just runs linting
testing
A skill with embedded malicious scripts
devops
Scanning cloud environment for leaks
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.