Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/opencue/cuecards/clawsec-nanoclaw)<a href="https://agentmods.dev/skills/opencue/cuecards/clawsec-nanoclaw"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/clawsec-nanoclaw/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/opencue/cuecards/clawsec-nanoclaw"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/clawsec-nanoclaw.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00035 | $0.02172 |
| Opus 5 | $0.00017 | $0.01086 |
| Sonnet 5 | $0.00007 | $0.00434 |
| Haiku 4.5 | $0.00003 | $0.00217 |
Grade B, and why
clawsec-nanoclaw scanned grade B with 2 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 9d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
trap 'rm -rf "$TMP_DIR"' EXIT Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL "$BASE/checksums.json" -o "$TMP_DIR/checksums.json" How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawSec for NanoClaw
Security advisory monitoring that protects your WhatsApp bot from known vulnerabilities in skills and dependencies.
Overview
ClawSec provides MCP tools that check installed skills against a curated feed of security advisories. It prevents installation of vulnerable skills, includes exploitability context for triage, and alerts you to issues in existing ones.
Core principle: Check before you install. Monitor what's running.
When to Use
Use ClawSec tools when:
- Installing a new skill (check safety first)
- User asks "are my skills secure?"
- Investigating suspicious behavior
- Regular security audits
- After receiving security notifications
Do NOT use for:
- Code review (use other tools)
- Performance issues (different concern)
- General debugging
MCP Tools Available
Pre-Installation Check
// Before installing any skill
const safety = await tools.clawsec_check_skill_safety({
skillName: 'new-skill',
skillVersion: '1.0.0' // optional
});
if (!safety.safe) {
// Show user the risks before proceeding
console.warn(`Security issues: ${safety.advisories.map(a => a.id)}`);
}
Security Audit
// Check all installed skills (defaults to ~/.Codex/skills in the container)
const result = await tools.clawsec_check_advisories({
installRoot: '/home/node/.Codex/skills' // optional
});
if (result.matches.some((m) =>
m.advisory.severity === 'critical' || m.advisory.exploitability_score === 'high'
)) {
// Alert user immediately
console.error('Urgent advisories found!');
}
Browse Advisories
// List advisories with filters
const advisories = await tools.clawsec_list_advisories({
severity: 'high', // optional
exploitabilityScore: 'high' // optional
});
Quick Reference
| Task | Tool | Key Parameter |
|---|---|---|
| Pre-install check | clawsec_check_skill_safety |
skillName |
| Audit all skills | clawsec_check_advisories |
installRoot (optional) |
| Browse feed | clawsec_list_advisories |
severity, type, exploitabilityScore (optional) |
| Verify package signature | clawsec_verify_skill_package |
packagePath |
| Refresh advisory cache | clawsec_refresh_cache |
(none) |
| Check file integrity | clawsec_check_integrity |
mode, autoRestore (optional) |
| Approve file change | clawsec_approve_change |
path |
| View baseline status | clawsec_integrity_status |
path (optional) |
| Verify audit log | clawsec_verify_audit |
(none) |
What ships with it
22 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.
- advisories/feed-signing-public.pem 113 B
- CHANGELOG.md 2.5 KB
- docs/INTEGRITY.md 14 KB
- docs/SKILL_SIGNING.md 15 KB
- guardian/integrity-monitor.ts 21 KB runs code
- guardian/policy.json 1.7 KB
- host-services/advisory-cache.ts 11 KB runs code
- host-services/integrity-handler.ts 9.6 KB runs code
- host-services/ipc-handlers.ts 3.3 KB runs code
- host-services/skill-signature-handler.ts 7.5 KB runs code
- INSTALL.md 9.4 KB
- lib/advisories.ts 11 KB runs code
- lib/local_file_io.ts 316 B runs code
- lib/risk.ts 2.4 KB runs code
- lib/signatures.ts 14 KB runs code
- lib/types.ts 5.7 KB runs code
- mcp-tools/advisory-tools.ts 13 KB runs code
- mcp-tools/integrity-tools.ts 8.1 KB runs code
- mcp-tools/signature-verification.ts 6.9 KB runs code
- README.md 5.1 KB
- skill.json 4.8 KB
- test/security-hardening.test.mjs 2.8 KB runs code
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.
- 9d ago First seen · 281 lines · 35 tokens per session scan B c735d0249dd9
clawsec-nanoclaw is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 2,172 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.
loongsuite-pilot-ops
Skill "loongsuite-pilot-ops" from alibaba/loongsuite-pilot, covering loongsuite-pilot-ops, quick start, todo: add quick start commands and usage.
atomic-visual-options
Planning-phase visual comparison aid. Renders 2-4 side-by-side variants per decision dimension as a single throwaway, self-contained HTML file and captures the user's pick as typed terminal codes (e.g. "A2 B3"). Auto-fires on phrases like "show me a few options", "mock up some variants", "let me see this side by…
atomic-wiki
Conversational wiki and capture-bucket routing. Fires when the user wants a place, space, or folder for notes, research, tickets, raw dumps, or knowledge capture — checks the block in /.claude/CLAUDE.md; if the cwd is under a registered realm, creates the folder as a bucket via atomic wiki bucket add rather than a…
atomic-review
Compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", or invokes /atomic-review. Auto-triggers when reviewing pull requests.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…