Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add yeaight7/agent-powerups --skill agent-config-security-auditgit clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/yeaight7/agent-powerups/agent-config-security-audit)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/agent-config-security-audit"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/agent-config-security-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/agent-config-security-audit"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/agent-config-security-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.01141 |
| Opus 5.5 | $0.00013 | $0.00456 |
| Sonnet 5.5 | $0.00007 | $0.00228 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
agent-config-security-audit scanned grade A with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- [ ] No auto-run instructions that would execute arbitrary commands on session start Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] No outbound network calls (`curl`, `wget`) in hooks without explicit user knowledge How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Config Security Audit
Systematic security review of agent configuration files. Run before committing config changes or onboarding a new repository.
When to Use
- After modifying any agent config file (
.claude/settings.json,.claude/mcp.json, AGENTS.md, hooks) - Before committing configuration changes to version control
- When onboarding a project with existing agent configs
- Periodic hygiene check (monthly or after a major dependency update)
Scope
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 |
Audit Checklist
Secrets and Credentials
- No API keys, tokens, or passwords hardcoded in any config file
- All secrets referenced as
$ENV_VARorprocess.env.*— never literal values -
.envand.env.localfiles are in.gitignore - MCP server
envfields contain variable references, not values
P0 (block immediately): Hardcoded secret in any committed file.
Permissions and Allow Lists
-
allowedToolsis scoped — noBash(*)wildcard granting unrestricted shell access -
deniedToolslist is present and non-empty for risky operations - MCP server tool scopes match the stated purpose of the server
- No
--no-verify,--force, or safety-bypass flags in hook commands
P0: Bash(*) or equivalent wildcard in allow list.
P1: No deniedTools list when Bash is in scope.
Hooks
- Hook commands use fixed strings — no
${file},${input}, or other user-interpolated variables - No outbound network calls (
curl,wget) in hooks without explicit user knowledge - Errors in safety hooks are not silently suppressed (
2>/dev/null,|| true) - PreToolUse hooks for high-risk tools (file delete, shell exec) are present
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 127 lines · 33 tokens per session scan A 9f4cdf196add
agent-config-security-audit is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,141 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 2 findings (unrestricted tool access, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-14.
Other skills, from other repositories
skill-authoring
Author SKILL.md: frontmatter, structure, writing principles.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
github-code-review
Review PRs: diffs, inline comments via gh or REST.
requesting-code-review
Pre-commit review: security scan, quality gates, auto-fix.
simplify-code
Sequential 3-lens cleanup of recent code changes.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.