Audit agent configuration files for security vulnerabilities and misconfigurations. Covers settings.json, .mcp.json, .codex/config.toml, AGENTS.md, hooks, plugin manifests, and relay config. Classify findings as P0 or P1.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Systematic security review of agent configuration files. Run before committing config changes or onboarding a new repository.
.claude/settings.json, .claude/mcp.json, AGENTS.md, hooks)Audit every config file present:
| File | Agent |
|---|---|
.claude/settings.json | Claude Code |
.claude/mcp.json (or project-root mcp.json) | Claude Code |
.codex/config.toml | Codex |
docs/AGENTS.md (project root) | Generic/Codex |
docs/CLAUDE.md (project root) | Claude Code |
hooks/ | Any |
plugins/*/plugin.json | Agent Powerups |
.apx/relay/*.json | apx relay |
$ENV_VAR or process.env.* — never literal values.env and .env.local files are in .gitignoreenv fields contain variable references, not valuesP0 (block immediately): Hardcoded secret in any committed file.
allowedTools is scoped — no Bash(*) wildcard granting unrestricted shell accessdeniedTools list is present and non-empty for risky operations--no-verify, --force, or safety-bypass flags in hook commandsP0: Bash(*) or equivalent wildcard in allow list.
P1: No deniedTools list when Bash is in scope.
${file}, ${input}, or other user-interpolated variablescurl, wget) in hooks without explicit user knowledge2>/dev/null, || true)P0: Command injection via interpolation in any hook. P1: Silent error suppression on a security or quality hook.
npx -y without a pinned version or digestdescription fieldP1: Unpinned npx -y auto-install in MCP server config.
P1: Auto-run instruction with shell exec; unconditional safety override.
plugins/NAME/.codex-plugin/plugin.json) declares tool access scoped to its purposelatest.apx/relay/) are in .gitignore| Severity | Definition | Response |
|---|---|---|
| P0 | Can directly compromise security or leak secrets | Fix before any commit; do not push |
| P1 | Increases attack surface or weakens safety controls | Fix before merging; document exception if deferred |
| Note | Best practice not followed, no direct risk | Fix in follow-up; log as tech debt |
Agent Config Security Audit — <project>/<date>
P0 findings:
[P0] <file>:<line> — <description>
Fix: <what to change>
P1 findings:
[P1] <file>:<line> — <description>
Fix: <what to change>
Notes:
[Note] <file> — <description>
Summary: <N> P0, <N> P1, <N> Notes
If no findings: state "No findings." explicitly.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
The English summary is being prepared. Showing the original description.
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
The English summary is being prepared. Showing the original description.
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project
The English summary is being prepared. Showing the original description.
Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).
The English summary is being prepared. Showing the original description.
You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.
The English summary is being prepared. Showing the original description.
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project
The English summary is being prepared. Showing the original description.