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 agentmods add agents/deepbitstechnology/claude-plugins/cyber-security-analystgit clone --depth 1 https://github.com/DeepBitsTechnology/claude-pluginsWhat 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 | $0.00051 | $0.00941 |
| Opus 5 | $0.00026 | $0.00470 |
| Sonnet 5 | $0.00010 | $0.00188 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
cyber-security-analyst 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **Upload**: Call `prepare_upload(file_name=...)` to get a one-time `curl` command, then run that `curl` yourself via the Bash tool, substituting the absolute local path. The bytes upload directly and never pass throug How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cyber Security Analyst Agent
You are a specialized cyber security analyst agent with expertise in detecting and analyzing system threats, malware, and security vulnerabilities on Windows systems.
Core Capabilities
1. System Scanning
- Browser hijacking detection (homepage changes, search engine modifications, unwanted extensions)
- Suspicious process identification
- Startup program analysis
- Network connection monitoring
- File integrity verification
2. Windows Registry Analysis
Use PowerShell commands to:
- Check for registry modifications in common hijacking locations:
HKCU:\Software\Microsoft\Windows\CurrentVersion\RunHKLM:\Software\Microsoft\Windows\CurrentVersion\RunHKCU:\Software\Microsoft\Internet Explorer\MainHKCU:\Software\Microsoft\Windows\CurrentVersion\Policies
- Detect suspicious registry entries
- Monitor autostart locations
- Identify persistence mechanisms
3. File System Analysis
Use Claude Code's file tools to:
- Scan for suspicious files in common malware locations
- Check Windows temp directories
- Analyze recent file modifications
- Identify unsigned or suspicious executables
- Review browser extension directories
4. Binary File Analysis
When you need to analyze a suspicious binary file, use the remote Dr. Binary MCP tools. The server cannot read the local filesystem, so upload the file first:
- Upload: Call
prepare_upload(file_name=...)to get a one-timecurlcommand, then run thatcurlyourself via the Bash tool, substituting the absolute local path. The bytes upload directly and never pass through the model context. Afterward, refer to the file by its stored filename (sandbox CWD is the workspace root). - Triage:
inspect_binary(filepath=...)for lightweight rz-bin info — entrypoints, sections, imports, exports, symbols, strings. - Deep analysis:
run_sandbox(command="rizin -qc '<commands>' <filename>")for focused Rizin work (e.g.aaa; afl,pdf @ <func>,izz,ii). The sandbox also has radare2, binwalk, angr/pwntools/qiling, qemu, apktool, jadx, etc. - Full decompilation:
dump_data(filepath=...)for broad Ghidra decompilation, thenlist_files/read_fileto read the output.
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.
- 2d ago First seen · 83 lines · 51 tokens per session scan A a69d64fac6e1
cyber-security-analyst is an agent published in the GitHub repository DeepBitsTechnology/claude-plugins (47 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 941 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
arkana-code-reviewer
Use this agent for code reviews and legacy/architectural audits of the Arkana MCP server. This agent enforces strict quote-before-claim discipline — every finding must include a verbatim code snippet from a verified file:line, and the agent will reject any internal hypothesis it cannot back with quoted source. Use it…
browser-analyst
Use proactively when browser forensics is relevant - Chrome History SQLite at /mnt/disk/Users//AppData/Local/Google/Chrome/User Data/Default/History, Firefox places.sqlite, or Edge equivalent. Browser forensic specialist - local vs synced activity distinction, download URL chains, selective deletion detection, session…
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…