agentleFS
vikas8520-codervikas8520-coder/nerve/skills/omni-auth/SKILL.md

omni-auth

Skill0 starsChanged 3 months agoMITView on GitHub

Manage API key authentication and session tokens. Start here to authenticate requests via Bearer token, obtain session cookies, and configure login requirements for the Nerve API.

  • Reads credentials
  • Sends data out

3 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 1 is common, 0 are distinctive, and 3 are very specific to this project.

  • 1

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All requests require a valid Bearer token or session cookie.

    line 13
  2. Common:

    Start OIDC login for the dashboard admin gate

    line 41
  3. Very specific:

    All requests: ${NERVE_URL}/v1/...

    line 89
  4. Very specific:

    Use data[].id as model field in requests.

    line 104

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

Overview

Manage API key authentication and session tokens. Start here to authenticate requests via Bearer token, obtain session cookies, and configure login requirements for the Nerve API.

Authentication

All requests require a valid Bearer token or session cookie. Obtain a token via POST /api/auth/login or configure REQUIRE_API_KEY=false for local development.

Endpoints

POST /api/auth/login

Authenticate user

curl -X POST https://localhost:20128/api/auth/login \
  -H "Authorization: Bearer $NERVE_TOKEN"
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/auth/logout

Log out

curl -X POST https://localhost:20128/api/auth/logout \
  -H "Authorization: Bearer $NERVE_TOKEN"
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/auth/oidc/login

Start OIDC login for the dashboard admin gate

Builds an authorization URL from the configured OIDC issuer/client (discovered via {issuer}/.well-known/openid-configuration, falling back to {issuer}/authorize), sets a short-lived oidc_state cookie, and redirects the browser. Password login remains available as a fallback while OIDC is enabled.

curl https://localhost:20128/api/auth/oidc/login \
  -H "Authorization: Bearer $NERVE_TOKEN"

GET /api/auth/oidc/callback

Complete OIDC login for the dashboard admin gate

Validates the state cookie, exchanges the authorization code for tokens, verifies the ID token against the issuer's JWKS (audience = client id), and — if oidcAllowedSubjects is configured — checks the token's sub/email against that allowlist. On success it mints the same 30-day auth_token dashboard-session JWT used by password login and redirects to /dashboard.

curl https://localhost:20128/api/auth/oidc/callback \
  -H "Authorization: Bearer $NERVE_TOKEN"

Payloads

See the full OpenAPI specification at GET /api/openapi/spec or docs/openapi.yaml for detailed request/response schemas.

<!-- skill:custom-start --><!-- Migrated from skills/nerve/SKILL.md (preserved curated content) -->

Nerve

Local/remote AI gateway exposing OpenAI-compatible REST. One key, 207+ providers, auto-fallback, RTK token saver, MCP server, A2A agents.

Setup

export NERVE_URL="http://localhost:20128"      # or VPS / tunnel URL
export NERVE_KEY="sk-..."                       # from Dashboard → API Keys

All requests: ${NERVE_URL}/v1/... with Authorization: Bearer ${NERVE_KEY}.

Verify: curl $NERVE_URL/api/health → {"ok":true}

Discover models

curl $NERVE_URL/v1/models                  # chat/LLM (default)
curl $NERVE_URL/v1/models/image            # image-gen
curl $NERVE_URL/v1/models/tts              # text-to-speech
curl $NERVE_URL/v1/models/embedding        # embeddings
curl $NERVE_URL/v1/models/web              # web search + fetch
curl $NERVE_URL/v1/models/stt              # speech-to-text

Use data[].id as model field in requests. Combos appear with owned_by:"combo".

Capability skills

CLI skills (nerve binary)

Errors

  • 401 → set/refresh NERVE_KEY (Dashboard → API Keys)
  • 400 Invalid model format → check model exists in /v1/models/<kind>
  • 503 Provider circuit open → upstream provider down; retry after Retry-After seconds
  • 429 → rate limited; honor Retry-After

Differentiators vs OpenAI direct

  • Auto-fallback combos (14 strategies): never stop coding even if a provider rate-limits
  • RTK token saver: tool_result compressed via 47 specialized filters (git-diff, test-jest, terraform-plan, docker-logs…) — 20-40% token reduction
  • Caveman mode: optional terse system prompt injection (LITE/FULL/ULTRA) — 15-25% completion reduction
  • MCP + A2A servers built-in (this is the only AI router that exposes both protocols)
  • Memory with FTS5 + Qdrant for persistent agent context
  • Guardrails for PII masking, prompt injection detection, vision policies
<!-- skill:custom-end -->

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.