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 EmpiricaAI/empirica --skill services-auditorgit clone --depth 1 https://github.com/EmpiricaAI/empiricaWrote 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/empiricaai/empirica/services-auditor)<a href="https://agentmods.dev/skills/empiricaai/empirica/services-auditor"><img src="https://agentmods.dev/badge/skills/empiricaai/empirica/services-auditor/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/empiricaai/empirica/services-auditor"><img src="https://agentmods.dev/badge/skills/empiricaai/empirica/services-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 105 Skill accesses MCP server configuration files (mcp.json). MCP configs contain server URLs, authentication tokens, and tool definitions — reading them allows the skill to discover and potentially abuse other tool integrations.Fix: Remove all code or instructions that read MCP configuration files (mcp.json). MCP server details should be managed by the agent runtime, not read by individual skills.
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.00126 | $0.02531 |
| Opus 5 | $0.00063 | $0.01265 |
| Sonnet 5 | $0.00025 | $0.00506 |
| Haiku 4.5 | $0.00013 | $0.00253 |
Grade A, and why
services-auditor 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 11d 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.
empirica finding-log --finding "PID 12345 (curl -N https://ntfy.sh/...) is an orphaned credentialed listener — parent PID 1, cmdline references ntfy auth env vars, age 14 days. Recommended: kill 12345 + investigate paren How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Services Auditor — AI judgment over a deterministic scanner snapshot
This skill fires when an AI agent is asked to reason about the running
state of an AI-touching machine. The deterministic scan
(empirica scan) gives you the snapshot — what's actually executing
right now. Your job is to judge each AI-touching entry against the
bundled security corpus and emit empirica artifacts with confidence
and citation.
You are not a separate process. You are the AI session that the user asked to audit. Run inside a normal empirica transaction.
When to use
- The user typed
empirica scan --explainand a system-reminder pointed you here. - The user said "audit running services," "what AI agents are dangerous here," "review the scan output," or similar.
- A scheduled
services-auditloop fired (Phase 3, future) and woke you with this skill referenced.
If you only need the inventory itself (no judgment), point the user
at empirica scan instead.
Phase 0 — PREFLIGHT
Open a transaction with the audit work_type so the Sentinel weights your evidence sources correctly:
empirica preflight-submit - <<'EOF'
{
"task_context": "Services audit — read the deterministic scanner snapshot at ~/.empirica/last_scan_<project_id>.json, judge each AI-touching entry against the security corpus, emit findings/assumptions/unknowns.",
"work_type": "audit",
"domain": "default",
"criticality": "medium",
"vectors": { "...": "YOUR assessment across the 13 vectors" },
"reasoning": "Audit transaction. Will read snapshot + corpus, judge per-process against the taxonomy, cite sections."
}
EOF
Phase 1 — Read inputs
Two files are load-bearing:
1. The scanner snapshot
Always read the most recent saved snapshot (the user gets this via
empirica scan --explain which auto-saves):
cat ~/.empirica/last_scan_<project_id>.json
If absent, run empirica scan --save yourself first, then read it.
2. The bundled security corpus
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.
- 11d ago First seen · 243 lines · 126 tokens per session scan A 27f7cd75f112
services-auditor is a skill published in the GitHub repository EmpiricaAI/empirica (246 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 2,531 once invoked, about $0.0006 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 skills, from other repositories
workflow-builder
Design, build, and maintain autonomous OpenClaw workflows (stewards). Use when creating new workflow agents, improving existing ones, evaluating automation opportunities, or debugging workflow reliability. Triggers on "build a workflow", "create a steward", "automate this process", "workflow audit", "what should I…
smart-delegation
Intelligent task delegation — route to think with deep reasoning for hard problems, or Grok for unfiltered takes. Teaches when to escalate, how to pack context into sub-agent spawns, and how to communicate delays transparently. Default: handle directly on chat (thinking off). Escalate only when the quality gain…
review
A pause before an artifact goes into the world. Reviews external comms, money, calendar, public posts, or send-as-operator actions through a small panel of independent lenses (empathy first) and returns a verdict of pass / edit / hold / block.
claude-code
Route real repo work to Claude Code instead of editing by hand. Triggers on "claude code" or "cc", and on any request to edit, fix, refactor, or open a PR in a repo outside /.openclaw/workspace. Claude Code picks up the repo's CLAUDE.md / AGENTS.md, applies its standards, and knows the /ai-coding-config:multi-review…
cortex
Personal knowledge compiler and memory system. Ingests raw sources (documents, notes, transcripts, captures) into a structured, interlinked knowledge base. Maintains living entity pages, learning analysis, and the MEMORY.md routing table. Replaces the librarian skill.
drive-to-done
Drive a task all the way to a verified done state — write DoD first, verify each item with evidence, stop only at named stop conditions.