verify-oceans-admin
Verify the Oceans LLM admin control plane and backend gateway against the real local stack, seeded demo data, and bounded live providers when required.
Install / Use
npx skills add ahstn/oceans-llm --skill verify-oceans-adminInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AI & Machine LearningSupported Platforms
Our assessment of verify-oceans-admin
verify-oceans-admin scores 70/100 on our quality scale, 874th of 947 AI & Machine Learning skills we index.
Its SKILL.md is 29 KB long, well organised into 12 sections with 19 code examples: a thorough specification that gives an agent plenty to work with.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-16. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
verify-oceans-admin compared with similar skills
All 4 of these similar skills score higher than verify-oceans-admin; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| verify-oceans-admin (this skill)by ahstn | 70 | 0 | — | SKILL.md |
| claude-memby thedotmack | 100 | 117.6k | today | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| Understand-Anythingby Egonex-AI | 100 | 92.8k | 1d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
Frequently asked questions
- How do I install verify-oceans-admin?
- Run
npx skills add ahstn/oceans-llm --skill verify-oceans-admin. The install tabs above show the steps for each supported agent. - Which AI agents does verify-oceans-admin work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is verify-oceans-admin safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is verify-oceans-admin still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubname: verify-oceans-admin
description: Verify the Oceans LLM admin control plane and backend gateway against the real local stack, seeded demo data, and bounded live providers when required. Use for user-path checks of sign-in, models, API keys, observability, usage costs, spend controls, batches, agent sessions, request logs, Anthropic Messages thinking and effort compatibility, MCP registry and tool access, OpenRouter routing, guardrails, and Skills storage.
compatibility: Requires mise, git, lsof, and Chromium via mise run //ui:e2e:install; macOS or Linux.
Verify Oceans Admin
Use this skill to drive the embedded TanStack Start admin UI through the gateway. The primary surface is the browser UI at /admin. The gateway API is a secondary surface for health checks, saved-state confirmation, bounded MCP tool calls, and bounded live LLM requests when the change affects the request path.
Read features/README.md before you choose a proof. Use the exact feature recipe for the path under test.
Plan
Start from the diff, not from memory. From the repository root:
.agents/skills/verify-oceans-admin/scripts/control-oceans-admin plan # against origin/main
.agents/skills/verify-oceans-admin/scripts/control-oceans-admin plan HEAD~1 --json
plan maps every changed and untracked path through features/routing.json. It prints RUN <feature> with the recipe and drive command (or manual recipe), flags paid proofs, and lists SKIPPED paths with a reason. When nothing reaches a runtime surface, it prints SKIP: no runtime surface; report that line instead of launching a stack. UNMAPPED paths need a decision. Pick the feature the path affects, run that proof, and add the glob to routing.json in the same change. plan needs no run ID and starts nothing.
Launch
Run all commands from the repository root. control-oceans-admin finds mise on PATH or at ~/.local/bin/mise; set MISE_BIN if it lives elsewhere. Select a unique run ID:
export OCEANS_VERIFY_RUN_ID="$(date -u +%Y%m%dT%H%M%SZ)-$$"
export OCEANS_VERIFY_GATEWAY_PORT=38090
export OCEANS_VERIFY_UI_PORT=33010
.agents/skills/verify-oceans-admin/scripts/control-oceans-admin launch
launch requires lsof for listener and checkout ownership checks. It runs the existing mise run dev-stack task with alternate ports through GATEWAY_PORT and UI_PORT, refreshes this checkout's gitignored gateway.db with the local demo seed, and records process IDs under /tmp/oceans-admin-verification/$OCEANS_VERIFY_RUN_ID/. It refuses to start if either selected port is in use or another gateway process has this repository as its working directory. A listener counts as this run's only when its working directory belongs to this checkout's git root, so a stack from another worktree that takes a selected port during startup fails the launch instead of being adopted. The launch also fails as soon as the dev stack exits, for example when its gateway cannot bind the port.
dev-stack receives OPENAI_API_KEY and OPENROUTER_API_KEY from fnox through its secrets grant in root mise.toml, not from the launching shell. Without a terminal, as when an agent runs launch, mise runs fnox without its daemon or 1Password prompts. Run mise run secrets-sync in the checkout first; new worktrees receive its encrypted cache through .worktreeinclude. Otherwise mise refuses to start the stack and names the key fnox could not resolve.
The refresh never recreates gateway.db, so rows that earlier runs created stay: onboarding users, audit entries, and the disabled servers every MCP proof leaves behind (servers have no delete API, so cleanup disables them). For a clean database, such as before capturing docs screenshots, run mise run //crates/gateway:reset-local-demo or move gateway.db aside before launch.
The instance is ready when launch prints ready and both /readyz and /api/v1/health answer. The sign-in URL is http://127.0.0.1:$OCEANS_VERIFY_GATEWAY_PORT/admin/login. Protected feature routes remain under /admin/*.
For Skills storage, set OCEANS_VERIFY_SKILLS=true before launch. The harness starts native RustFS through the rustfs mise profile and creates a private run-local configuration, database, and synthetic service-account key. See features/skills.md for the full recipe. This option leaves gateway.db unchanged.
This checkout cannot run two verification stacks safely because ordinary runs would both write gateway.db. The checkout lock also applies to Skills verification. A stack in another checkout has a separate database and is safe when ports differ. Do not drive a pre-existing instance.
Teardown uses the recorded process IDs:
.agents/skills/verify-oceans-admin/scripts/control-oceans-admin cleanup
Shared machine state
- Cargo output. Root
mise.tomlsetsCARGO_TARGET_DIR={{config_root}}/targetin[env], and mise applies it over the caller's shell, so exportingCARGO_TARGET_DIRbeforelaunchordrivehas no effect. Final binaries such asdebug/gatewayanddebug/oceansstay in this checkout'starget/, so a build in another checkout cannot replace the binary a proof is using. Intermediate artifacts go to a central per-checkout build dir throughCARGO_BUILD_BUILD_DIR. - pitchfork version warning. mise supervises daemons through one per-user pitchfork supervisor shared by every checkout. If the
pitchforkCLI was upgraded since that supervisor started, commands warn about a CLI and supervisor version mismatch. The warning is harmless for verification. Do not restart the supervisor from a verification run, because that stops daemons other checkouts rely on. When nothing else needs them, the user can runpitchfork supervisor stopand let the nextmisedaemon command start a current one.
Doctor
Run the read-only doctor check before browser work and whenever the UI looks stale:
.agents/skills/verify-oceans-admin/scripts/control-oceans-admin doctor
Doctor confirms that the selected gateway and UI ports are still owned by their recorded listener PIDs and that those processes run from this checkout, checks /readyz, and records the gateway service version from /api/v1/health. The short-lived launcher PID can exit after mise has started both listeners. A failed ownership check means this instance is not safe to drive.
Drive
The harness is control-oceans-admin. It uses the repository's installed Playwright package and Chromium. It drives ARIA roles, accessible labels, route paths, and existing test IDs from crates/admin-ui/web.
Prove the Models path:
.agents/skills/verify-oceans-admin/scripts/control-oceans-admin drive models
The Models driver runs the idempotent mise run //ui:e2e:install task to ensure Chromium is available. It then opens the protected /admin/api-keys route, captures its redirect to sign-in, signs in as the seeded admin@local user, follows the Models sidebar link, checks the displayed count against rendered rows and the total count against the read-only admin models response, checks the always-visible Intelligence Index against that response, checks every platform-admin Model info section, enables the optional Context window and Capabilities columns, and opens Client config for gpt-6-astra.
Prove the Leaderboard and Agent Harnesses paths together:
.agents/skills/verify-oceans-admin/scripts/control-oceans-admin drive observability
The Observability driver opens the protected Leaderboard route, signs in, and compares both the
Leaderboard and Agent Harnesses desktop tables with their production admin API responses for the
seeded 7-day window. It selects the 31-day range on both pages and repeats the comparison. The proof
also requires the new leaderboard columns, harness token columns, a Mastra row with its Lobe icon,
and an Oh My Pi row with its white omp.sh mark.
Features whose routing entry says manual have no driver yet. Follow their recipe with any browser automation your harness offers (Playwright via mise exec -- node, a built-in browser, or an MCP browser). Apply the same proof rules as a driver: capture the entry action, capture the resulting state, and check API parity. Save screenshots into the run's evidence directory, then write the proof with control-oceans-admin record (see Proofs). The admin UI is server-rendered, so wait for network idle after each navigation before you fill fields; values typed before hydration are silently discarded. Read counts only after the list re-renders, not straight after the URL changes.
For other features, follow the exact stable handles in the feature map. Extend the driver with a named command before you report a new path as automated.
Prove backend gateway routing and generated-tool guardrails through OpenRouter:
.agents/skills/verify-oceans-admin/scripts/control-oceans-admin drive backend-gateway
The Backend Gateway driver opens the real API Keys page, creates a temporary user key limited to deepseek-v4.1-flash, evaluates one synthetic destructive command without executing it, and sends one bounded forced-tool Chat Completions request through OpenRouter. It confirms the request-linked guardrail decision and request-log attempt, writes sanitized evidence, revokes the key, and confirms that the revoked key is rejected. Use features/backend-gateway.md for the exact contract.
Prove service tiers through OpenRouter:
.agents/skills/verify-oceans-admin/scripts/control-oceans-admin drive service-tiers
The Service Tiers driver creates a temporary key for the tier canary models, checks tier discovery and four free rejections (unknown tier, conflicting fields, policy-blocked tier, no route for the tier), then sends six short paid requests: default, priority and flex A/B on gpt-6-luna, the route-forced gpt-6-luna-fast, Anthropic speed: "fast" on claude-haiku-5.5, and a streamed priority request. It compares OpenRouter's per-token prompt cost across tiers, checks the requested and served tier in each request log, screenshots the request detail, and revokes the key. Use features/service-tiers.md for the exact contract.
Prove the inference endpoints and the OpenCode plugin in real clients:
.agents/skills/verify-oceans-admin/scripts/control-oceans-admin drive harness-integration
The plan selects this proof for changes to the chat, Responses and Messages handlers, model discovery, generated client configs, and packages/opencode-oceans. The driver needs a run ID and OPENROUTER_API_KEY, but no launched stack: tests/harness-integration builds the gateway from this checkout and starts a temporary one. It runs the harness x model matrix (OpenCode plugin, Pi, Oh-My-Pi and Claude Code with GPT-6 Luna, Claude Haiku 5.5 and Gemini 4 Hydrogen), the per-harness MCP checks, and the packed-plugin suite, and records one check per test. Use features/harness-integration.md for the exact contract.
Prove the MCP registry, Tool Sets workbench, grants, and live tool routing:
export OCEANS_VERIFY_MCP_CANDIDATES_FILE=/absolute/path/to/mcp-candidates.json
.agents/skills/verify-oceans-admin/scripts/control-oceans-admin drive mcp
Read features/mcp.md before launch. It defines the required gateway credential aliases and the candidate file. The aliases must be exported in the launching shell; launch records their names, and the driver trusts that record rather than its own environment. The MCP driver creates temporary servers, two tool sets, and one API key through the UI. One server points at https://unreachable.invalid/mcp to prove how a failed discovery is reported without contacting a real host. It verifies saved me
Truncated for display — read the full file on GitHub.
Related Skills
claude-mem
117.6kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Understand-Anything
92.8kGraphs that teach > graphs that impress. Turn any code into an interactive knowledge graph you can explore, search, and ask questions about. Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and more.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
