Back to Directory/Security & Auth

Aegis Security Skills

Read-only library of 24 defensive cybersecurity skills: ATT&CK, ATLAS, DFIR, CTEM and more.

Security & AuthTypeScriptv1.5.0

An independent open-source project, maintained by Drupad Sachania. Two products, one repository:

AegisThemis
What24 security skills, an installer and a read-only MCP serverA security-operations agent that plans, fans out to Aegis skills, checks every output and writes a version-stamped report
Calls a model?Never. It is markdown and JSONUses your assistant (plugin) or your own key or a local model (standalone)
Packageaegis-skills@aegis-skills/themis-plugin and @aegis-skills/themis

Status: Aegis 1.5.0 is on npm as aegis-skills, and the Claude Code plugin installs straight from this repository. The website is live. Themis is in development, local-first and not published as an app yet (run it from a checkout, see docs/themis); its two libraries, @aegis-skills/themis-core and @aegis-skills/themis-gateway, are on npm. The status table below says what is done and what is next.


Aegis

Aegis mark

Defensive security skills in the open Agent Skills format. One source installs natively into coding assistants, is served over the Model Context Protocol, and flattens into a single-file prompt for any chat AI.

Skill library: 24 skills across 5 families

FamilySkills
Frameworksmitre-attack · mitre-atlas · mitre-engage
Threat Intelattack-surface-mapping · exposure-validation · threat-hunting · threat-intel-synthesis · threat-modeling
Response & Analysisdigital-forensics · malware-analysis · reverse-engineering · security-operations
Domain Defenceapplication-security · data-loss-prevention · deception-engineering · endpoint-security · identity-access-management · infrastructure-security · network-security · operational-technology
Governance & Riskcompliance · governance · risk-management · security-documentation

Each skill is a workflow of phases (methodology references) plus a live-threat-intel phase. Skill content is updated monthly. Browse them at aegis-skills.vercel.app.

Quick start

# Install the skills into your tool's native skills folder and register the MCP server
npx aegis-skills install --platform claude      # codex | gemini | cursor | vscode | antigravity | all
npx aegis-skills install --platform claude --project   # this project only

# Serve the whole library over MCP on stdio
npx aegis-skills mcp

Claude Code plugin: /plugin marketplace add drupadsachania/aegis-skills, then /plugin install aegis-skills@aegis-skills.

Needs Node.js 24 or later.

CLI commands

CommandWhat it does
aegis install [--platform <id>] [--project]Copy the skills into each tool's native folder and register the MCP server (config files are backed up first). init is an alias
aegis uninstall [--platform <id>] [--project]Remove only what Aegis installed; edited files are kept as .bak
aegis updateRe-sync every recorded install with the installed version
aegis list [--json]Bundled skills and recorded installs
aegis mcpServe the skill library over MCP on stdio

Installed skills refresh automatically after an upgrade; set AEGIS_NO_AUTO_REFRESH=1 to turn that off.

Using a skill without installing

Every skill page on the website offers a single-file prompt (all phases flattened, stamped "Intel as of ") and a skill zip, and the whole library is available from the hosted MCP server. Build the prompts locally with npm run build:prompts (written to dist/prompts/, not committed).

MCP

Three read-only tools are offered: list_skills, get_skill, get_skill_phase. They serve public skill content only and never call a model.

{
  "mcpServers": {
    "aegis": { "command": "npx", "args": ["-y", "aegis-skills", "mcp"] }
  }
}

Hosted, with nothing to install (Streamable HTTP, no authentication): https://aegis-skills.vercel.app/api/mcp.


Themis

Themis mark

Give Themis a task such as "validate exposure to CVE-2026-12345 on our VPN gateways". It runs a fixed seven-step workflow: validate, decompose, schedule, fan out to Aegis skills, guardrail, synthesise and audit. Deterministic steps are plain code in themis-core; reasoning steps are done by a model.

Themis on your AIThemis standalone
ModelYour assistant (Claude Code, Codex, Gemini CLI)Your Anthropic, OpenAI or Gemini key, or a local model (Ollama, LM Studio)
InterfaceYour assistant's chat, through the themis-mcp MCP serverA local web dashboard on 127.0.0.1
ApprovalsYour client's MCP elicitation prompt, otherwise handed back to youThe dashboard's Approvals page
InstallAn MCP config (a marketplace listing is planned)npx @aegis-skills/themis dashboard

Governance is enforced in code, not by the model:

  • External tools are classified read, write or execute. Every call, read included, becomes an approval request that only a human can approve; approved reads also run within a call budget.
  • Access is default-deny: a server is reachable only by the skills in its allowedSkills.
  • Secrets are redacted, tool output is size-capped and wrapped as untrusted, and every step, call and decision goes to a local audit log in ~/.themis.
  • In plugin mode, tools you connect directly to your assistant bypass Themis and are not governed.

Read more: Themis docs and docs/themis.


Where things stand

StateNext
Aegis skills, CLI, MCPBuilt and tested on Linux, macOS and Windows (Node 24); 24 skills at version 1.5.0Released: aegis-skills@1.5.0 is on npm. Next: marketplace and directory listings
Website and hosted MCPLive at aegis-skills.vercel.appInstall commands are live
themis-core, themis-gatewayBuilt and tested; packaged and ready for npmReleased right after Aegis
Themis plugin and standalone appWorking from a checkout; no real-model run recorded in CI yetPublic beta: a model-backed end-to-end run, a clearer approval confirmation, diagnostics and issue templates
Marketplace listingsAegis first, as a skills-only pluginThemis follows once the beta settles

How this is maintained

  • CI on every change. Tests run on Ubuntu, macOS and Windows with Node 24, plus lint, dependency and layout guards, a production site build, and install smoke tests of each package. Releases are published by a tag-driven workflow with provenance, not from a laptop.
  • Skill content is refreshed monthly. Every flattened prompt is stamped with the date of its intel.
  • Dependencies are pinned and watched. GitHub Actions are pinned to full commit SHAs and kept current by Dependabot.
  • Defaults are conservative. Aegis never calls a model. Themis denies tool access by default, a human approves every external call, and prompts are redacted before they reach a model provider. Skills never make network or API calls themselves.

Found a bug or a skill that is out of date? Open an issue. For a vulnerability, use private reporting instead, as described in SECURITY.md.


Links


Development

npm install
npm run dev                         # http://localhost:3000
npx jest                            # tests for every package
npm run build                       # production build
npm run check:deps                  # dependency guards
node scripts/check-layout.js        # layout guard
npm run lint:skills                 # skill format lint

The site lives in apps/web; npm run dev -w @aegis-skills/web starts it. Requires Node.js 24 or later.

Project structure

├── apps/web/            # the website: catalogue, docs hub, downloads, hosted MCP (no model calls)
├── packages/
│   ├── aegis/           # aegis-skills: 24 skills, installer CLI, MCP server
│   ├── themis-core/     # deterministic workflow, redaction, approvals, local store
│   ├── themis-gateway/  # governed MCP client for external tools
│   ├── themis-plugin/   # Themis on your AI (MCP server, orchestrator skill, agents)
│   └── themis-app/      # Themis standalone (CLI and local dashboard)
├── scripts/             # repo scripts: lint, guards, prompt builder
├── docs/{aegis,themis,web}/   # user documentation, published by the website
└── .claude-plugin/      # Claude Code marketplace manifest

License

Licensed under either of Apache License, Version 2.0 or MIT license at your option (SPDX: Apache-2.0 OR MIT). See LICENSE and, for reporting vulnerabilities, SECURITY.md.

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y aegis-skills

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-drupadsachania-aegis-skills": {
      "command": "npx",
      "args": [
        "-y",
        "aegis-skills"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

aegis-skillsnpm

Compatible MCP Clients

Aegis Security Skills works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More