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 FlorianBruniaux/claude-code-plugins --skill cyber-defense-teamgit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/cyber-defense-team)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/cyber-defense-team"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/cyber-defense-team/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/florianbruniaux/claude-code-plugins/cyber-defense-team"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/cyber-defense-team.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.00050 | $0.00844 |
| Opus 5 | $0.00025 | $0.00422 |
| Sonnet 5 | $0.00010 | $0.00169 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
cyber-defense-team 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 4d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cyber Defense Team Skill
Orchestrate a 4-agent pipeline that analyzes log files for security threats and produces an incident report.
Pipeline Architecture
[You] -> Team Lead (this skill)
|
|-[1]-> log-ingestor (haiku) -> cyber-defense-events.json
|
|-[2]-> anomaly-detector (sonnet) -> cyber-defense-anomalies.json
| (reads events.json)
|-[3]-> risk-classifier (sonnet) -> cyber-defense-risk.json
| (reads anomalies.json)
`-[4]-> threat-reporter (sonnet) -> cyber-defense-report.md
(reads all 3 JSON files)
Stages 2 and 3 are sequential (each depends on previous output). Stage 4 runs after all data is ready.
Execution Steps
Step 1: Validate Input
Check that the log file exists (or that log content was provided inline). If the path doesn't exist, tell the user immediately and don't proceed.
Step 2: Spawn Log Ingestor
Use the Agent tool to spawn the log-ingestor agent:
Task: Parse the log file at [log_path] and write structured events to cyber-defense-events.json.
Log path: [log_path]
Wait for completion. Confirm cyber-defense-events.json was created.
Step 3: Spawn Anomaly Detector
Use the Agent tool to spawn the anomaly-detector agent:
Task: Read cyber-defense-events.json and detect anomalies. Write results to cyber-defense-anomalies.json.
Wait for completion. If anomalies_found: 0, skip to Step 5 (reporter still runs).
Step 4: Spawn Risk Classifier
Use the Agent tool to spawn the risk-classifier agent:
Task: Read cyber-defense-anomalies.json and classify overall risk. Write result to cyber-defense-risk.json.
Step 5: Spawn Threat Reporter
Use the Agent tool to spawn the threat-reporter agent:
Task: Read cyber-defense-events.json, cyber-defense-anomalies.json, and cyber-defense-risk.json. Generate a complete incident report and save it to cyber-defense-report.md.
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.
- 4d ago First seen · 115 lines · 50 tokens per session scan A aa8efca46c66
cyber-defense-team is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 7d ago), licensed MIT. It adds 50 tokens to every session and 844 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
content
Content production and SEO writing skills. Blog posts, long-form content research, structured content frameworks, audience-targeted writing, content optimization. Triggers on: blog, content writing, article, copywriting, content strategy, content brief, SEO content, audience research.
expo-app-config
Choosing between app.json vs app.config.ts vs app.config.js, environment variables, variants, extra fields, plugin chain, and slug/scheme/bundle/version discipline. Triggers on app.json, app.config.ts, app.config.js, expo config, environment variable, .env, eas secret, variant, extra field, slug, scheme, bundle…
expo-modules
Writing Swift/Kotlin native modules with the Expo Modules API, requireNativeModule, async functions, view modules, and the event-emitter pattern. Triggers on expo modules, native module, swift, kotlin, requireNativeModule, expo-module-scripts, expo.modules.json, view module, event emitter, native function, async…
expo-notifications
Push and local notification setup with expo-notifications. iOS (APNs) + Android (FCM) credentials, permission flow, channels (Android 8+), categories, and scheduled notifications.
expo-config-plugin
Writing Expo config plugins, withInfoPlist, withAndroidManifest, withDangerousMod, mod compose, plugin testing, and registration in app.config.ts. Triggers on config plugin, with-plugin, withInfoPlist, withAndroidManifest, withDangerousMod, withEntitlementsPlist, withGradleProperties, mod, native config, expo plugin…
expo-dev-client
Custom development builds with expo-dev-client, build profiles, a custom dev menu, runtime-version compatibility, and EAS Update integration. Triggers on expo-dev-client, dev client, custom dev build, development build, dev menu, expo go, runtime version, debug build, dev launcher, scan qr, dev server.