Jarvis Registry is a gateway that connects AI copilots and autonomous agents to enterprise tools through the Model Context Protocol and agent-to-agent communication. Organizations use it to manage identity, permissions, tool discovery, orchestration, logging, and observability, while the catalogue entries support agent workflows with it.
Borrowing it
Nothing to install: this file belongs to ascending-llc/jarvis-registry. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ascending-llc/jarvis-registry/main/.github/skills/local-frontend-check/SKILL.mdgit clone --depth 1 https://github.com/ascending-llc/jarvis-registryWrote 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/ascending-llc/jarvis-registry/local-frontend-check)<a href="https://agentmods.dev/skills/ascending-llc/jarvis-registry/local-frontend-check"><img src="https://agentmods.dev/badge/skills/ascending-llc/jarvis-registry/local-frontend-check/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ascending-llc/jarvis-registry/local-frontend-check"><img src="https://agentmods.dev/badge/skills/ascending-llc/jarvis-registry/local-frontend-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00052 | $0.01107 |
| Opus 5 | $0.00026 | $0.00553 |
| Sonnet 5 | $0.00010 | $0.00221 |
| Haiku 4.5 | $0.00005 | $0.00111 |
Grade A, and why
local-frontend-check 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 13d 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Frontend Check Skill
Fixed Configuration
| Setting | Value |
|---|---|
| Base URL | http://localhost/gateway |
| Browser session | Named jarvis — keeps a stable, reusable identity across runs |
| Launch flags | --persistent --headed — profile saved to disk, browser window visible |
| Backend log container | <cwd-basename>-registry-1 — where <cwd-basename> is the basename of your current working directory (e.g. if CWD is /projects/jarvis-registry, use jarvis-registry-registry-1) |
Workflow
Follow these phases in order every time this skill is invoked. Do not skip phases.
Phase 1 — Open the browser
playwright-cli -s=jarvis open http://localhost/gateway --persistent --headed
Then take a snapshot to read the page's current state:
playwright-cli -s=jarvis snapshot
Phase 2 — Handle authentication
Inspect the snapshot.
If the app loads directly (no login form, no auth redirect visible): the persistent profile is still valid. Skip to Phase 3.
If a login page or auth redirect is visible: the session has expired or this is a first run. Do the following:
- Tell the user: "The browser window is open and showing a login page. Please log in in the headed browser window, then confirm here when done."
- Use
AskUserQuestionto wait for the user's confirmation before continuing. - Take a second snapshot and verify the app has loaded (URL is no longer the login page, and the main app UI is visible). If still on the login page, tell the user and repeat.
Because --persistent saves the profile to disk, subsequent runs will pick up the stored session automatically and this phase will be skipped.
Phase 3 — Orient and navigate
Read the user's description of what to check. Navigate to the relevant section of the UI:
- Use
playwright-cli -s=jarvis goto <url>for direct navigation. - Use
playwright-cli -s=jarvis snapshot --depth=3to get a lightweight view of a complex page. - Use
playwright-cli -s=jarvis click <ref>to follow navigation links or open panels.
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.
- 13d ago First seen · 120 lines · 52 tokens per session scan A 483a3fb9b528
local-frontend-check is a skill published in the GitHub repository ascending-llc/jarvis-registry (2,828 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 1,107 once invoked, about $0.0003 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
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
capturing-proof
This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…
storybook-ui
Use when storybook for UI component development — stories, addons, controls, a11y testing, visual regression. Use when working with storybook ui.
ui-data-testid
Add stable data-testid attributes by default for new or refactored UI components. Use when implementing React/TSX views, shadcn/antd-style components, dropdown/menu configs, or interactive UI flows that need reliable selectors for unit/E2E tests.