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 strikersam/autonomous-ai-agency --skill risky-module-reviewgit clone --depth 1 https://github.com/strikersam/autonomous-ai-agencyWrote 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/strikersam/autonomous-ai-agency/risky-module-review)<a href="https://agentmods.dev/skills/strikersam/autonomous-ai-agency/risky-module-review"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/risky-module-review/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/strikersam/autonomous-ai-agency/risky-module-review"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/risky-module-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.00890 |
| Opus 5 | $0.00023 | $0.00445 |
| Sonnet 5 | $0.00009 | $0.00178 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
risky-module-review scanned grade A with 0 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 12d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: risky-module-review
Risky Modules in This Repo
| File | Risk | What to check |
|---|---|---|
admin_auth.py |
Session auth, admin identity | No secret leaks, session fixation prevention, proper expiry |
key_store.py |
API key persistence | Keys hashed before storage, no plaintext in logs, file permissions |
agent/tools.py |
Filesystem write surface | Path traversal prevention, content sanitization |
proxy.py (auth middleware) |
Bearer token validation | No bypass paths, rate limit correctness |
agent/loop.py (_local_safety_check) |
Security guardrail | Not weakened or removed |
Instructions
Step 1 — Read the module's AGENTS.md
agent/→agent/AGENTS.mdrouter/→router/AGENTS.md- No module AGENTS.md? Read the file header docstring carefully.
Step 2 — Checklist by module
admin_auth.py checklist
- Admin password is read from environment — never hardcoded
- Sessions expire (check
max_ageorSESSION_MAX_AGE) -
AdminIdentityis validated before any state-mutating action - No
print()orlog.debug()exposes the admin password or session token - CSRF protection present for state-mutating routes
key_store.py checklist
- API keys are stored hashed (SHA-256 or stronger) — never plaintext
-
keys.jsonis never committed (it is in.gitignore) - Key comparison uses constant-time comparison (
hmac.compare_digest) - No key value appears in any log line
-
issue_new_api_keyreturns the plaintext key exactly once, immediately
agent/tools.py checklist
-
apply_diffresolves paths withPath.resolve()and validates they stay withinself.root - No
..traversal path accepted without rejection - File content is not
eval()-ed orexec()-ed -
search_codedoes not expose.envorkeys.jsoncontent
proxy.py auth middleware checklist
-
verify_api_key()cannot be bypassed by setting a header to empty string - Rate limit is per-key, not per-IP (IP can be spoofed)
-
VALID_API_KEYSfrom env is populated — empty set should reject all requests
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.
- 12d ago First seen · 96 lines · 45 tokens per session scan A b418e87314e0
risky-module-review is a skill published in the GitHub repository strikersam/autonomous-ai-agency (8 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 890 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
codebase-sync
Convention discovery and rule generation from codebase analysis. Scans project structure, builds search indexes, identifies patterns, and generates enforceable rules.
code-review-patterns
Multi-dimensional code assessment across security, quality, performance, and maintainability with confidence-gated reporting (>=80%) and Router Contract generation.
code-review-orchestration
6-agent parallel code review orchestration covering architecture, security, performance, testing, quality, and documentation dimensions with weighted scoring.
code-review-pipeline
Multi-dimensional code review across correctness, security, performance, and maintainability with confidence-gated reporting and remediation loops.
orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
plan-implementation
Disciplined execution of approved plans with step-by-step verification, phase checkpoints, failure investigation, and mandatory code/security reviews.