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 OpenCoven/coven --skill openclaw-trustgit clone --depth 1 https://github.com/OpenCoven/covenWrote 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/opencoven/coven/openclaw-trust)<a href="https://agentmods.dev/skills/opencoven/coven/openclaw-trust"><img src="https://agentmods.dev/badge/skills/opencoven/coven/openclaw-trust.svg" alt="Measured on agentmods" 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.00043 | $0.00519 |
| Opus 5 | $0.00022 | $0.00260 |
| Sonnet 5 | $0.00009 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
openclaw-trust 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 8d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenClaw Trust
Use this skill when the user asks about security posture, threat modeling, attack vectors, trust boundaries, or safe rollout decisions for OpenClaw automations.
Source of truth
- Repo:
openclaw/trust - Core files:
threats.yaml— machine-readable threat modelCONTRIBUTING.md— how to submit threats/mitigations/chains
- Public render:
trust.openclaw.ai/trust/threatmodel - Vulnerability reporting:
[email protected]
What to apply in practice
1) Default to the highest-risk classes first
Prioritize controls for risks repeatedly marked high/critical in the trust model:
- Prompt injection (direct + indirect)
- Malicious skills / compromised skill updates
- Token theft from local config
- Tool argument injection and command execution abuse
- MCP/tool over-permission
2) Translate trust model into concrete controls
When recommending hardening, prefer specific actions:
- Default-deny sender/channel access (
AllowFromleast privilege) - Approval gates for state-changing actions
- Strict tool argument validation (no free-form shell interpolation)
- Limit/monitor skill install/update sources
- Least-privilege MCP server config
- Audit logs for new sender authorization + sensitive actions
- Token hygiene (rotation, minimize plaintext exposure)
3) Separate threat reporting vs vuln disclosure
- Threat model additions/updates →
openclaw/trustissues/PRs - Live exploitable vulnerabilities → responsible disclosure via Trust page/security email
Contribution pattern (for writing trust updates)
When drafting a new threat proposal, include:
- scenario + attack path
- affected OpenClaw components
- rough risk estimate
- suggested mitigation(s)
Maintainers will map to MITRE ATLAS tactic/technique + assign IDs.
Fast mental checklist for risky automation
- Can untrusted content reach prompt/tool parameters?
- Is there a hard approval gate before side effects?
- Could this run with broader permissions than required?
- Is sender/tool/source authenticated and allowlisted?
- Are outputs validated before execution/posting/sending?
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.
- 8d ago First seen · 65 lines · 43 tokens per session scan A 9bc078e4ac54
openclaw-trust is a skill published in the GitHub repository OpenCoven/coven (47 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 519 once invoked, about $0.0002 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
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
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.
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.
package-installer
Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.