synpulse8-opensourcesynpulse8-opensource/pulse8-ai-cortex-knowledge-vault/.cursor/skills/cortex-auth/SKILL.md

cortex-auth

Skill15 starsChanged 5 months agoApache-2.0View on GitHub

Cortex authentication — AUTH_METHOD none/apikey/oidc, API_KEY, OIDC, middleware, MCP ApiKeyGuard. Use for login, x-api-key, or securing endpoints.

Reads credentials

In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cortex-apiSkill
- cortex-compilerSkill
- cortex-contributingSkill
- cortex-deploySkill
- cortex-feedbackSkill
- cortex-graph-searchSkill
- cortex-mcpSkill
- cortexSkill
- cortex-vaultSkill

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Protected: all other /api/v1/*
line 29
Distinctive:
Use bearer token on API calls
line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Cortex auth

Configuration (`cortex/config.py`)

Env (also `CORTEX_*`)	Field	Purpose
`AUTH_METHOD`	`auth_method`	`none`, `apikey`, `oidc`
`API_KEY`	`api_key`	Shared secret for REST + MCP
`OIDC_*`	`oidc_*`	Provider URLs, client id/secret, redirect

Loaded via Pydantic Settings with CORTEX_ prefix and unprefixed aliases in .env.

REST middleware

cortex/auth/middleware.py — AuthMiddleware on FastAPI app.

Public paths (no auth):

/api/v1/health, /api/v1/login, /api/v1/auth/callback
/mcp, /.well-known/, /docs, /redoc, /openapi.json

Protected: all other /api/v1/*

Mode	Client sends
`apikey`	Header `x-api-key: <API_KEY>`
`oidc`	`Authorization: Bearer <token>`; API key accepted as fallback if set
`none`	No credentials

MCP auth

cortex/mcp/http_server.py — ApiKeyGuardMiddleware when auth_method == apikey.

Clients (Cursor, curl) must send x-api-key on POST /mcp/ and subsequent MCP requests.

OIDC flow

GET /api/v1/login → redirect to IdP
GET /api/v1/auth/callback → exchange code, issue session/token
Use bearer token on API calls

FastMCP may use OIDCProxy for browser-based MCP login in oidc mode.

Local development

AUTH_METHOD=none   # simplest
# or
AUTH_METHOD=apikey
API_KEY=dev-secret

scripts/env_check.sh prompts for auth-related vars when applying defaults.

Related skills

MCP HTTP: cortex-mcp
Deploy secrets: cortex-deploy

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free