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/synpulse8-opensource/pulse8-ai-cortex-knowledge-vault/cortex-contributingnpx skills add synpulse8-opensource/pulse8-ai-cortex-knowledge-vault --skill cortex-contributinggit clone --depth 1 https://github.com/synpulse8-opensource/pulse8-ai-cortex-knowledge-vaultWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/synpulse8-opensource/pulse8-ai-cortex-knowledge-vault/cortex-contributing)<a href="https://agentmods.dev/skills/synpulse8-opensource/pulse8-ai-cortex-knowledge-vault/cortex-contributing"><img src="https://agentmods.dev/badge/skills/synpulse8-opensource/pulse8-ai-cortex-knowledge-vault/cortex-contributing.svg" alt="Measured on agentmods" height="20"></a>What 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.00036 | $0.00494 |
| Opus 5 | $0.00018 | $0.00247 |
| Sonnet 5 | $0.00007 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
cortex-contributing 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 5d ago.
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.
What it actually says
Contributing to Cortex
Development setup
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest
Example vault: example_vault/ (or set VAULT_PATH).
Test layout
| Area | Path |
|---|---|
| API | tests/test_api.py |
| MCP | tests/test_mcp.py |
| Feedback | tests/test_feedback.py |
| Teams | tests/test_teams_notify.py |
| Graph | tests/test_graph*.py |
Run focused: pytest tests/test_feedback.py -v
Adding an MCP tool
- Implement handler in
cortex/mcp/tools.py - Register in
cortex/mcp/http_server.pyandcortex/mcp/server.py - Add REST route in
cortex/api/routes.pyif mirrored - Tests in
tests/test_mcp.py(+test_api.pyif REST) - Update
.cursor/skills/cortex-mcp/reference.mdand README MCP table - Mention in
AGENTS.mdskill index if user-facing
Code conventions
- Match existing logging:
logger = logging.getLogger(__name__) - Config via
get_settings()fromcortex/config.py - Vault paths always relative to vault root
- Minimize scope; no drive-by refactors
Agent documentation
| File | Purpose |
|---|---|
AGENTS.md |
Always-on repo map for agents |
.cursor/skills/cortex/SKILL.md |
Master router skill |
.cursor/skills/cortex-*/SKILL.md |
Topic skills |
Do not install project skills under ~/.cursor/skills-cursor/ (reserved for Cursor built-ins).
Pre-commit / CI
Follow project hooks if configured. Fix test failures before claiming done.
Related skills
- Master index:
cortex - Full spec:
docs/superpowers/specs/2026-05-29-cursor-skills-design.md
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.
- 5d ago First seen · 66 lines · 36 tokens per session scan A 74bf6e4b12ef
cortex-contributing is a skill published in the GitHub repository synpulse8-opensource/pulse8-ai-cortex-knowledge-vault (14 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 494 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
background-task
Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
rag-knowledge
Work with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vectorstore }} + {{…
alembic-migration
Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
billing-stripe
Work with Stripe billing — subscriptions, plans/prices, the Customer Portal, credits, usage metering, invoices, and webhook events. Use when changing plans, handling a new Stripe webhook, debugging a payment/subscription flow, or touching credit balances and usage.