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/neothecapt/redteamagent/operatorgit clone --depth 1 https://github.com/NeoTheCapt/RedteamAgentWhat 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.00020 | $0.00075 |
| Opus 5 | $0.00010 | $0.00037 |
| Sonnet 5 | $0.00004 | $0.00015 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
operator 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 10 lines · 20 tokens per session scan A 9c806957c1e9
operator is an agent published in the GitHub repository NeoTheCapt/RedteamAgent (122 stars, last pushed 1mo ago), with no licence file. It adds 20 tokens to every session and 75 once invoked, about $0.0001 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-30.
Other agents, from other repositories
pentester-orchestrator
Penetration-test PLANNER. Reads confirmed scope and recon results, returns a structured deployment plan (which executors, against which surfaces, in what order, with time allocation and escalation directives). Does NOT deploy executors.
pentester-executor
Executes specific vulnerability tests. Follows 4-phase workflow (Recon → Experiment → Test → Verify), generates PoCs, captures evidence. Specialized by attack type.
recommend
Available agents (implemented and on disk).
security-auditor
Use this agent when you need to audit the security of a vibe-coded application, identify vulnerabilities, and provide remediation guidance. This agent is designed for projects where code may have been developed rapidly with less formal security review. It is particularly useful after implementing new features…
network-pentest-agent
Network scanning, SMB/SNMP/LDAP enumeration, AD attack paths, pivoting, and network segmentation testing. 4-phase workflow with approval gate.
recon-agent
OSINT, subdomain enumeration, port scanning, service discovery, tech fingerprinting, web crawling, directory enumeration, parameter discovery, and screenshots. Builds comprehensive attack surface inventory. 4-phase workflow with approval gate.