naksha-browse

naksha-browse is a command for Claude Code from Adityaraj0421/naksha-studio. It costs 23 tokens per session (2,279 once invoked), scanned A, original, MIT.

A browser-based design research and inspection command. It visits a web address, studies how the interface looks and behaves, and saves the findings to project memory.

In plain words
What is it for?
Use it to study design patterns on an external website or check whether your own interface matches its intended design. It requires a web address and can use a research or inspection mode.
Why use it?
It removes the need to rely only on screenshots or memory when reviewing a website. It can distinguish between researching another site and inspecting your own local or staging site.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

Part of the naksha-studio plugin — 47 commands, 7 agents shipped together

Good fit Use it to study design patterns on an external website or check whether your own interface matches its intended design. It requires a web address and can use a research or inspection mode.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/adityaraj0421/naksha-studio/naksha-browse
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Adityaraj0421/naksha-studio

Made for: Claude Code.

Or install naksha-studio, the plugin that ships this one along with the rest of its 47 commands, 7 agents.

Wrote 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.

agentmods badge for naksha-browse

README.md
[![agentmods](https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/naksha-browse/github.svg)](https://agentmods.dev/commands/adityaraj0421/naksha-studio/naksha-browse)
Your own site
<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/naksha-browse"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/naksha-browse/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.

agentmods 80×15 button for naksha-browse

Your own site · 80×15
<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/naksha-browse"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/naksha-browse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,279 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.02279
Opus 5 $0.00012 $0.01140
Sonnet 5 $0.00005 $0.00456
Haiku 4.5 $0.00002 $0.00228

Measured 12d ago against content hash de5f0c652298, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

naksha-browse 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 12d 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.

commands/naksha-browse.md · 240 lines

How it starts

The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/naksha-browse $ARGUMENTS

You are a Design Researcher and UX Analyst. Your job is to visit a URL, observe it with trained design eyes, extract meaningful visual and interaction patterns, and save those findings to project memory so future naksha commands can learn from them.

Input: $ARGUMENTS

Step 0: Parse Arguments

Extract from $ARGUMENTS:

  • url (required): The URL to browse. Must start with http:// or https://. If no URL is provided, ask the user: "Which URL should I browse?"
  • --mode (optional): research or inspect.
    • research — external URL, studying design patterns for inspiration or competitive analysis.
    • inspect — your own UI (localhost or staging), checking how it actually looks vs. intent.
    • Auto-detect if omitted: if the URL host is localhost, 127.0.0.1, or 0.0.0.0, default to inspect. Otherwise default to research.

Step 1: Playwright Availability Check

Before navigating anywhere, probe the browser connection:

Attempt to call mcp__plugin_playwright_playwright__browser_navigate with url: "about:blank".

  • If the call succeeds → continue to Step 2.
  • If the call fails or the tool is not found → stop and show:
╔══════════════════════════════════════════════════════════╗
║  naksha-browse — Browser Unavailable                     ║
╚══════════════════════════════════════════════════════════╝

  /naksha-browse requires the Playwright MCP connection.
  Playwright is not available in this environment.

  To enable:
  1. Install the Playwright MCP server:
     npx @playwright/mcp@latest

  2. Add it to your Claude Code MCP config and restart.

  Alternatively, provide a screenshot manually:
  → Run /design-score --screenshot <path> for visual analysis
  → Run /design-audit for code-based design review

Step 2: Load Project Context (optional)

Search up to 3 directory levels for .naksha/project.json:

find . -maxdepth 3 -name "project.json" -path "*/.naksha/*" 2>/dev/null | head -1

Read the full file on GitHub · 240 lines

Changes

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.

  1. 12d ago First seen · 240 lines · 23 tokens per session scan A de5f0c652298

Subscribe to this mod's changes

naksha-browse is a command published in the GitHub repository Adityaraj0421/naksha-studio (318 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 2,279 once invoked, about $0.0001 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.