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 agentmods add skills/agentweave/cortex/joinnpx skills add agentweave/cortex --skill joingit clone --depth 1 https://github.com/agentweave/cortexWhat 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 | $0.00041 | $0.02939 |
| Opus 5 | $0.00020 | $0.01470 |
| Sonnet 5 | $0.00008 | $0.00588 |
| Haiku 4.5 | $0.00004 | $0.00294 |
Grade A, and why
join scanned grade A with 0 findings 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 yesterday.
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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/join — Join the Cortex Agent Team
Onboard this agent to Cortex by reading its config from the team directory and generating the local protocol file.
Arguments
<agent-name> — the agent's name (e.g., "Billing Dev", "Chief of Staff"). If not provided, ask: "What is this agent's name in Cortex?"
Steps
1. Read config
Read ~/.cortex/config.yaml to get team_dir, heartbeat_minutes, daily_briefing, and daily_review.
If config doesn't exist, stop and respond:
"Cortex is not set up yet. Run
/setupfirst."
2. Resolve name and slug
Use the provided <agent-name>.
Derive the slug: lowercase, replace spaces with hyphens, strip any characters that are not alphanumeric or hyphens.
3. Read agent note
Read <team_dir>/agents/<slug>/<slug>.md.
If the file doesn't exist, stop and respond:
"Agent
<name>is not registered in Cortex. Run/register <name>to create the agent note first."
4. Extract config from agent note
From the frontmatter and body, extract:
name— from frontmatterslug— derived from nameproject— from frontmatter (the project directory path)projects— from ## Projects section (list of project slugs)role— from ## Role section (first line after heading)
5. Determine if this is a re-run
Check if .cortex.md exists in the current working directory. If it does, this is a sync (re-run).
6. Generate .cortex.md
Write .cortex.md in the current working directory.
If the agent slug is chief-of-staff, generate the coordinator .cortex.md (see Section A below).
Otherwise, generate the worker .cortex.md (see Section B below).
Replace all {placeholder} values with the actual extracted values.
7. Update CLAUDE.local.md
Read the CLAUDE.local.md in the current working directory.
If it exists and does NOT already contain the text "## Cortex":
- Append this section at the very end:
## Cortex
On session start, run /join <name> to sync with Cortex. See .cortex.md for full protocol.
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.
- yesterday First seen · 327 lines · 41 tokens per session scan A ecc6c3f0c852
join is a skill published in the GitHub repository agentweave/cortex (12 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 2,939 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
markstream-react
Integrate the beta markstream-react package into a React 18+ or Next app. Use when Codex needs to add the React renderer, choose the root, next, or server entrypoint, import CSS correctly, choose between content and nodes, keep client boundaries safe, add renderer-local streamingComponents or htmlComponents, use…
web-scraping
Fetches web pages and extracts structured data using mq's toolchain (mq-crawl for fetching/crawling/JS rendering, mq for HTML-to-Markdown selector-based extraction, http() for in-query requests). Use when the user wants to scrape a URL, pull structured data out of a webpage, crawl a site, or turn HTML into…
markstream-vue2-cli
Integrate markstream-vue2 into a Vue 2 Vue CLI or Webpack 4 app. Use when Codex needs Webpack 4-friendly setup, CDN worker fallbacks for Mermaid or KaTeX, dist/index.css imports, Vue 2 composition-api shims, or code block choices limited to stream-diffs or plain .
markstream-svelte
Integrate the beta markstream-svelte package in Svelte 5 or SvelteKit apps. Use when Codex needs Svelte 5 runes, CSS and optional peers, smooth streaming, worker setup, renderer-local or scoped custom components, or SSR-safe boundaries. Svelte 4 is unsupported.
task-planning-arch
计算任务 gap 并产出下一步可执行子任务 List[TaskSpec];gap 已闭返回空数组。对齐 arch 场景(架构师名册/技术栈概览/双视角分析)确定式分解——按根目标交付物集合 + donechildren 查表(参照 task-planning storage 特例,非自由 LLM 分解)。.
task-search
在框架预查的候选 bot 集里决出执行者(who)与协作方式(how),返回 4 态 SearchResult(HITSINGLE/HITGROUP/HITMULTIBOTS/MISS)。对齐案例剧本确定式映射。.