Subagent

Vex

Security Engineer. Use proactively when the team adds an integration, exposes an endpoint, stores user data, wires an authenticated flow…

Type: Subagent
Repository: myICOR/myPKA
GitHub stars: 303
License: CC-BY-SA-4.0
Repo last updated: Sep 26, 2026
Source file: README.md

What Vex is

Vex is a subagent published in the myICOR/myPKA repository on GitHub, which has about 303 stars. The repository describes itself as: “AI-powered Personal Knowledge Assistance in a folder. Built on the ICOR methodology. Plain markdown. Any LLM. Yours forever.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Vex and get back a compact result.

How to install Vex

Claude Code

Download README.md from the repository.
Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from README.md, shared under the repository's CC-BY-SA-4.0 license. Read the full file on GitHub.

An AI team with clear roles, shared instructions and memory across sessions. It already knows ICOR. Open it in Claude Code, Codex, Gemini CLI or Cursor.

> Coming from myPKA v5? 6.0.0 has a new shape. It doesn't update your v5 folder, and nothing forces you to move. Your v5 folder keeps working, and v5.5.2 stays downloadable from its release page. When you're ready, follow MIGRATING-FROM-5.md, step by step.

What myPKA is

myPKA (My Personal Knowledge Assistance) is the architecture for an AI team that works with you. This repository is a ready-made team built on it: the agents, their contracts, the procedures they follow and the scripts that check their work.

ICOR is the methodology: how you take things in, keep them under control, turn them into output and refine the loop.
ICOR for Life is where you put ICOR into practice. It works fully without AI.
myPKA is the AI team you add when you want help. It works on your ICOR for Life folder.

The team gives your AI better context, a clear job for every agent, procedures it can repeat and a record of what happened last session. It doesn't make the model smarter, and it doesn't make every answer right. You stay in charge, and you review the work.

The team

You talk to Larry, the orchestrator. He hands each job to the right specialist and brings the result back. Ten specialists work with him, from Penn, who files your notes and your journal, to Nolan, who hires a new specialist when a job has no owner. The full team, with every job, is in README-myPKA.md.

Works with your AI

AGENTS.md is the one entry file, for every host.

Get started

Download mypka.zip from the latest release.
Check that it's genuine with the GitHub CLI. Put your version in place of , as one line:

   gh attestation verify mypka-<version>.zip --repo myICOR/myPKA --signer-workflow myICOR/myPKA/.github/workflows/release-mypka.yml --source-ref refs/tags/v<version> --deny-self-hosted-runners

Continue only if it prints that verification succeeded. mypka.zip is the same bytes and checks with the same command.

Choose where it lives:

Mode A, inside your ICOR for Life folder. One folder holds both. The two products share no file names, so neither overwrites the other. No extra setup.
Mode B, in its own folder next to your ICOR for Life folder. You copy one file, .mypka/sources.yaml, that tells the team where your content is.

Open the folder in your AI and say hello to Larry.

The full steps, including mode B and moving from ICOR for Life 1.34, are in README-myPKA.md. That file also ships inside the download.

Today the team works on an ICOR for Life folder on your own disk. Coming: connecting myPKA to an ICOR for Life setup in Notion or Tana. No connector ships in 6.0.0.

Updating

From the folder that holds AGENTS.md:

python3 "06 AI Team/AI Team Knowledge/Scripts/mypka-update.py" --release ~/Downloads/mypka-<version>.zip

That's a dry run: it prints the plan and writes nothing. Read it, then run the same command with --live to apply it. The updater never deletes a file, and it never overwrites a file you edited: our new version lands beside yours as .update.

Before you install

Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
Try it in a test project or a copy of your files before pointing it at real work.
Pin the version you tested, and review changes before updating.
Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Vex?

Vex is a subagent for Claude Code and Claude Cowork from the myICOR/myPKA repository on GitHub. Security Engineer. Use proactively when the team adds an integration, exposes an endpoint, stores user data, wires an authenticated flow…

How do I install Vex in Claude Code?

Download README.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Vex in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Vex safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under CC-BY-SA-4.0. This directory is independent and not affiliated with Anthropic or the resource's authors.