Semia

Semia

**Security audit for AI agent skills.** Know what a skill *can* do before you trust it.

[](https://github.com/berabuddies/Semia/actions/workflows/ci.yml) [](https://github.com/berabuddies/Semia/actions/workflows/lint.yml) [](https://codecov.io/gh/berabuddies/Semia) [](LICENSE) [](pyproject.toml)

Agent skills are markdown files with embedded shell commands, network calls, and tool invocations. They run with **your credentials, on your machine, with your data**. Semia reads a skill as data — never executes it — and produces an evidence-backed report of every capability it may exercise.

It is the difference between

*"I trust this skill because the README looks fine."*

and

*"I trust this skill because Semia extracted 14 actions, 6 effects, and 2 secret reads — and every one is grounded in a specific source line."*

---

Quick example

Pick whichever fits how you already work.

As a CLI

pip install semia-audit
semia scan ./some-skill

`scan` does prepare → synthesize (via your configured LLM provider) → detect → report in one shot. Output lands under `.semia/runs//` by default — pass `--out ` to override. You'll need an LLM provider configured first — see [Set up an LLM provider](#set-up-an-llm-provider) below.

Inside Codex, Claude Code, or OpenClaw

Install the plugin once. Each host has its own flow.

**Codex** — pick either path:

*Shell (scripts and CI):*

codex plugin marketplace add berabuddies/Semia

Then enable the plugin by appending to `~/.codex/config.toml`:

[plugins."semia@semia"]
enabled = true

*Intera