agents-security

Audit local AI-agent configurations and session transcripts for risky permissions, secrets, and commands.

4|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/yeaboi-ai/yeaboi.ai --skill agents-security-yeaboi-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agents-security
Source: https://github.com/yeaboi-ai/yeaboi.ai/tree/main/claude-plugin/yeaboi/skills/agents-security
Command: npx skills add https://github.com/yeaboi-ai/yeaboi.ai --skill agents-security-yeaboi-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents accumulate risky settings over time: permission-bypass flags, wildcard allow rules, risky hooks, unvetted MCP servers, and secrets pasted into session transcripts. This Skill scans that local setup, tells you which findings actually mattered, and applies fixes. ## Core Features & Use Cases - Deterministic security scan: Audits settings, MCP configs, and session transcripts for permission bypasses, wildcard rules, secret-shaped text, and risky shell commands, with a verdict per finding (needs-decision, unsure, test-data, handled). - Session replay and signals: Replays the redacted turns around any flagged line so you can see whether a command actually ran or was just written into a file. - One-click fixes: Applies guard hooks, settings edits, PRs against the session repository, key rotation guidance, or dismissals, and tracks posture changes across scans over time. - Use Case: Ask how safe your Claude Code setup is; the scan finds a wildcard Bash allow rule and an API key pasted in a transcript, replays the context, and offers a guard hook plus a rotation link. ## Quick Start Ask the assistant to run an agent security scan of my local AI-agent setup and show me any findings that need a decision.

Frequently Asked Questions about agents-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my Claude Code agent security settings?

Run the agents_security_scan tool, which audits your settings files, MCP configurations, and session transcripts for risky patterns. The report leads with a verdict line and lists issues in priority order, each with an explanation and available fixes.

How to check if an AI agent ran a risky command?

Use the replay function on a finding's key to see the redacted transcript turns before and after the flagged line. The verdict distinguishes commands that actually ran from text that was only written into a file or test fixture.

Does the agent security scan detect leaked API keys?

Yes, it detects secret-shaped text such as sk- prefixed keys and user:password URLs in transcripts and configs. Findings are redacted with the matched span masked, and a transcript match is treated as a rotation signal rather than a checked-in secret.

What fixes can be applied to agent security findings?

Available fixes include writing a PreToolUse guard hook, editing a settings key after backup, opening a PR against the session repository, rotating a key via the provider's page, or dismissing and marking findings as test data. Applied fixes show as handled on the next scan.

Is a clean agent security scan a guarantee the setup is safe?

No. The checks are deterministic pattern scans, so a clean report only means no known pattern matched, not that the setup is safe. The Skill is labeled beta and its findings are indicators, not a full security audit.