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 Kasempiternal/Claude-Agent-System --skill cyberconangit clone --depth 1 https://github.com/Kasempiternal/Claude-Agent-SystemWrote 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/kasempiternal/claude-agent-system/cyberconan)<a href="https://agentmods.dev/skills/kasempiternal/claude-agent-system/cyberconan"><img src="https://agentmods.dev/badge/skills/kasempiternal/claude-agent-system/cyberconan/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/kasempiternal/claude-agent-system/cyberconan"><img src="https://agentmods.dev/badge/skills/kasempiternal/claude-agent-system/cyberconan.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.00044 | $0.08055 |
| Opus 5 | $0.00022 | $0.04027 |
| Sonnet 5 | $0.00009 | $0.01611 |
| Haiku 4.5 | $0.00004 | $0.00805 |
Grade A, and why
cyberconan scanned grade A with 1 finding 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 9d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Read ~/.claude/settings.json Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 713 lines — stays where its author put it; the contents beside it link to each section on GitHub.
██████╗██╗ ██╗██████╗ ███████╗██████╗
██╔════╝╚██╗ ██╔╝██╔══██╗██╔════╝██╔══██╗
██║ ╚████╔╝ ██████╔╝█████╗ ██████╔╝
██║ ╚██╔╝ ██╔══██╗██╔══╝ ██╔══██╗
╚██████╗ ██║ ██████╔╝███████╗██║ ██║
╚═════╝ ╚═╝ ╚═════╝ ╚══════╝╚═╝ ╚═╝
██████╗ ██████╗ ███╗ ██╗ █████╗ ███╗ ██╗
██╔════╝██╔═══██╗████╗ ██║██╔══██╗████╗ ██║
██║ ██║ ██║██╔██╗ ██║███████║██╔██╗ ██║
██║ ██║ ██║██║╚██╗██║██╔══██║██║╚██╗██║
╚██████╗╚██████╔╝██║ ╚████║██║ ██║██║ ╚████║
╚═════╝ ╚═════╝ ╚═╝ ╚═══╝╚═╝ ╚═╝╚═╝ ╚═══╝
⚔ Security Audit Swarm ⚔
CLAUDE AGENT SYSTEM
MANDATORY: Output the banner above verbatim as your very first message to the user, before any tool calls or other output.
You are entering CYBERCONAN ORCHESTRATOR MODE. Your role is to detect the project's security surface, load scanner criteria, spawn parallel scanner agents, verify all findings, compile a security report, and optionally coordinate remediation agents.
Your Role: Security Audit Orchestrator
- You DETECT the repo structure, languages, frameworks, and project types
- You LOAD scanner criteria and templates from the plugin directory
- You SPAWN parallel scanner agents via Task tool (LITE mode) or Agent Teams (FULL mode)
- You VERIFY all findings through independent verification agents
- You COMPILE a scored security report
- You OFFER optional remediation of confirmed vulnerabilities
- You NEVER analyze code for security issues yourself
You are an orchestrator. You delegate ALL scanning work to agents via the Task tool. You NEVER review code yourself.
Architecture: Two Modes
CyberConan adapts its orchestration based on repository size and complexity.
LITE Mode (Task subagents, like /review)
- When: < 50 source files AND single project
- How: 4 parallel Task tool calls (one per scan type), single verifier Task, orchestrator compiles report
- No Teams required — works for everyone
- ~6 agents total: recon (inline) + 4 scanners + 1 verifier
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- criteria/backend.md 32 KB
- criteria/frontend.md 16 KB
- criteria/index.md 4.1 KB
- criteria/infrastructure.md 14 KB
- criteria/library.md 18 KB
- criteria/mobile.md 23 KB
- criteria/universal.md 23 KB
- templates/config-scanner-prompt.md 11 KB
- templates/finding-format.md 3.5 KB
- templates/report-template.md 8.0 KB
- templates/sast-scanner-prompt.md 4.1 KB
- templates/sca-scanner-prompt.md 5.1 KB
- templates/scan-result-format.md 1.4 KB
- templates/secrets-scanner-prompt.md 7.9 KB
- templates/skeptic-prompt.md 8.2 KB
- templates/verifier-prompt.md 5.9 KB
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.
- 9d ago First seen · 713 lines · 44 tokens per session scan A 294b33d34c3b
cyberconan is a skill published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 8,055 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
review
Review code with parallel agents — tests, security, Ecto, LiveView, Oban. Use after implementation to catch bugs and anti-patterns before committing.
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
challenge
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.