In development
Themis
A security-operations agent built on Aegis. Give it a task, such as "validate exposure to CVE-2026-12345 on our VPN gateways". It plans the work, fans it out to specialist skills, checks every output, and writes a report stamped with the exact Themis and Aegis versions it used.
Status: in development. Themis is local-first and still being matured. The plugin (1.1.0) and the standalone app (0.1.0) are built and tested in the repository, and you can run both from a checkout today (see Install). They are not published to npm or AI directories yet; that will be announced here.


Two ways to run
| Themis on your AI | Themis standalone | |
|---|---|---|
| Where the model runs | Your assistant (Claude Code, Codex, Gemini CLI) | Your API key (Anthropic, OpenAI, Gemini) or a local model (Ollama, LM Studio) |
| API key needed | No | Yes, or a local model |
| Interface | Your assistant's chat | Local web dashboard on 127.0.0.1 |
| Orchestration | Your assistant runs each step, guided by the Themis skill | LangGraph runs the same workflow definition |
| Approvals | Asked through your client's own prompt when it supports MCP elicitation; otherwise handed back for you to run | Approvals page in the dashboard |
| Tool governance | Tools you register with Themis are governed; tools connected straight to your assistant are not | Every tool call is governed |
| History and audit | Local SQLite in ~/.themis | Local SQLite in ~/.themis |
| Install | An MCP config (a marketplace listing is planned) | npx @aegis-skills/themis dashboard |
The workflow
Deterministic steps are plain code in themis-core and behave the same in both modes. Reasoning steps are done by your assistant (plugin) or by the configured model (standalone).
Governance and approvals
- Every external tool is classified read, write or execute.
- Every call, read included, waits for a person to approve it. An approved read runs within a per-run call budget and timeout; secrets are redacted and the output is wrapped as untrusted data.
- Writes and executes become approval requests. Only a human can approve: the dashboard's Approvals page, or your client's own MCP prompt. No tool, graph node or model output can approve.
- Every call, result and decision is written to the audit log.
- An unreachable tool server degrades to "no tools"; it never crashes a run.
Honest boundary: in plugin mode, tools you connect directly to your assistant bypass Themis and are not governed or audited. Register security tools with Themis to govern them. Governance details →
Provenance and approval
Every run carries a version stamp: the Themis core, the installed Aegis pack and the skill-format (osk) version. A real stamp from this repository:
{
"themis": "0.1.0",
"aegis": "1.5.0",
"osk": "1.1"
}Themis 0.1.0 · Aegis 1.5.0 (osk 1.1)
Standalone reports end with that line and carry the stamp in their JSON export. In plugin mode the stamp is returned with each run payload and with the report. The stamp names the Aegis package installed next to Themis, so check it if you registered a different Aegis server separately.
The approval boundary sits at execution: the gateway runs an external call only if its approval is approved and decided by a human, and only once. Trust and data flow lists what runs where and how to verify it.
Screenshots
Where to get it
| Status | Where | |
|---|---|---|
| Aegis | Available | On npm as aegis-skills 1.5.0, and as a Claude Code plugin from the GitHub repository. Directory listings are coming. The website, the downloads and the hosted MCP work today. |
| Themis | In development | Local-first today: run it from the repository. Marketplace and directory distribution is planned for a later milestone, once its tool contract is stable and a supported remote endpoint exists. |
These are plans, not promises, and they carry no dates. Anything that changes will be announced on this site.
Install
The npm and marketplace commands below are the planned installs and do not work yet. Run Themis from the repository today.
Run from the repository
Needs Node.js 24 or later and a checkout of the repository. Standalone dashboard:
git clone https://github.com/drupadsachania/aegis-skills cd aegis-skills npm ci npm run build -w @aegis-skills/themis node packages/themis-app/bin/themis.js dashboard
Plugin mode: build the plugin, then register the built server with your assistant (the commands are in the plugin guide).
npm run build -w @aegis-skills/themis-core -w @aegis-skills/themis-gateway -w @aegis-skills/themis-plugin node packages/themis-plugin/dist/index.js
Plugin mode, planned install (no API key)
Themis is being matured locally and is not published yet. It will be announced here and is not available through AI directories yet. You can run it today from the repository — see the Themis docs.
Not in the Claude Code marketplace yet: the marketplace lists Aegis only, until the Themis plugin is published to npm. Run it from the repository today.
Standalone dashboard, planned install (your key or a local model)
Themis is being matured locally and is not published yet. It will be announced here and is not available through AI directories yet. You can run it today from the repository — see the Themis docs.
Needs Node.js 24 or later. No Docker, no build tools.
npx @aegis-skills/themis dashboardVersions
Themis reads skills from any installed Aegis with the same osk major version. Monthly skill updates and new skills are picked up automatically; an osk major bump needs a Themis release. The plugin uses your installed Aegis; the standalone app bundles its own. Version compatibility →
Skills only: hosted MCP. Trust: security and license.