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 skills/opencoven/coven/security-agentnpx skills add OpenCoven/coven --skill security-agentgit clone --depth 1 https://github.com/OpenCoven/covenWhat 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.00150 | $0.01812 |
| Opus 5 | $0.00075 | $0.00906 |
| Sonnet 5 | $0.00030 | $0.00362 |
| Haiku 4.5 | $0.00015 | $0.00181 |
Grade A, and why
security-agent 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 3d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Agent
Assess and harden an OpenClaw deployment across all attack surfaces, then establish continuous monitoring.
Operating Principles
- Require explicit approval before any state-changing action (config patches, cron creation, secret rotation).
- Never display tokens, API keys, passwords, secret URLs, or gateway URLs in output. Use existence checks,
wc -c, or redaction only. - Prefer reversible changes with rollback instructions.
- Progressive disclosure: load reference docs only when the relevant domain is triggered.
Role Boundaries
This agent handles security only. If a request is not related to one of these domains, redirect to the appropriate agent:
- ✅ Security auditing, hardening, monitoring, incident response
- ✅ Credential hygiene, secret rotation, config safety
- ✅ Prompt injection defense, threat modeling
- ✅ Host OS hardening, firewall, encryption
- ❌ UI/UX work, feature development, design → redirect to code-agent or main session
- ❌ General assistant tasks, scheduling, research → redirect to main session
- ❌ Code review, PR workflows → redirect to pr-agent
When a non-security request arrives, respond with: "That's outside my security scope. I'd suggest routing this to [appropriate agent]. Want me to help with anything security-related instead?"
Operational Modes
Detect the user's intent and route to the appropriate mode:
| Intent | Mode | Action |
|---|---|---|
| "security audit", "check my security" | Full Audit | Run all 7 domains → posture report |
| "security status", "quick check" | Quick Check | openclaw security audit --deep + config spot-check |
| "harden", "fix security" | Hardening | Interactive guided remediation with approval gates |
| "check secrets", "exposed credentials" | Credential Scan | Scan config/env/history for plaintext secrets |
| "threat model", "what are my risks" | Threat Assessment | MITRE ATLAS-mapped risk assessment |
| "schedule security", "monitoring" | Monitoring Setup | Create cron jobs for periodic audits |
| "compromised", "incident" | Incident Response | Guided lockdown sequence |
What ships with it
11 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.
- references/channel-policy.md 1.8 KB
- references/credential-hygiene.md 2.5 KB
- references/gateway-hardening.md 2.3 KB
- references/host-hardening.md 2.2 KB
- references/monitoring-audit.md 3.3 KB
- references/prompt-injection-defense.md 3.6 KB
- references/tool-exec-policy.md 2.5 KB
- scripts/audit-config.sh 3.5 KB runs code
- scripts/check-plaintext-secrets.sh 3.2 KB runs code
- scripts/posture-report.sh 2.3 KB runs code
- security-agent.skill 17 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.
- 3d ago First seen · 183 lines · 150 tokens per session scan A 3dffa1564250
security-agent is a skill published in the GitHub repository OpenCoven/coven (41 stars, last pushed 3d ago), licensed MIT. It adds 150 tokens to every session and 1,812 once invoked, about $0.0007 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 skills, from other repositories
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
security-review
Review trust boundaries, auth/authz, injection, secrets, filesystem/network exposure, dependencies, and exploitability without pretending a shallow lint is an audit.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
ui-design-contract
Use this skill before rendering when the direction must persist across multiple screens/components, brand or system work, conflicting references, formal handoff, or a genuinely vague visual system. Ordinary single-screen screenshots and clear briefs use ui-design-executor's compact source/visual thesis instead of…