agentleFS
modu-aimodu-ai/moai-adk/.claude/skills/moai-ref-aside-browser/SKILL.md

moai-ref-aside-browser

Skill1.3k starsChanged 2 months agoApache-2.0View on GitHub

Safe-use reference for the optional Aside browser agent (the `aside` command-line tool and its MCP server), which works inside the operator's own logged-in browser. Covers when the orchestrator may use it, how its permission modes work, and the rules that keep it read-only by default. Operated by the orchestrator alone. NOT for: public pages that a plain fetch can read, subagent work, or CI runs.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 5 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 3 mentionsOct 2026: 3 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the modu-ai/moai-adk repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about modu-ai/moai-adk

The biggest 5 of 16 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 16

Talked about on GitHub (16 times).

On GitHub · 16

11 more on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use it for a task that needs a page behind the operator's login, which a fresh headless browser cannot reach, and only when the operator …

    line 30
  2. Distinctive:

    Do not use it for public pages (a plain fetch or the platform default browser tooling reads those), in CI, or because it happens to be …

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Aside Browser (optional)

Purpose

Aside is an optional browser agent that acts inside the operator's own browser, so it sees every page the operator is signed in to, with the operator's credentials, cookies, and history. aside mcp starts an MCP server over stdio with two tools: exec runs the browser agent on logged-in sites, and repl runs Playwright-style JavaScript against open pages (120-second timeout; page starts unset, so call openTab(url) or getTabs() first). Flag and tool names here reflect one observed version; if a probe or a call fails, treat Aside as absent.

When to use, and when not

  • Use it for a task that needs a page behind the operator's login, which a fresh headless browser cannot reach, and only when the operator asked for it.
  • Do not use it for public pages (a plain fetch or the platform default browser tooling reads those), in CI, or because it happens to be installed.

Who operates it

Aside is operated by the orchestrator alone. A subagent never invokes Aside, neither the aside command nor the Aside MCP tools; a task that needs Aside returns a blocker report to the orchestrator, which runs the step itself or drops it.

Safe-use rules

  1. Permission. Never pass --permission full-access, and never request full-access by any other route (settings, prompts, or tool arguments).
  2. Guard by omission. The permission flag takes one of three values; ask and guard are the same Guard mode, and omitting the flag also means Guard. Prefer to omit --permission entirely so the default Guard applies.
  3. REPL limit. aside repl has no permission flag, so its read-only limit is discipline, not enforcement: restrict REPL work to navigation, reading, and screenshot operations.
  4. Writes. Any step that changes state (submitting a form, posting, purchasing, deleting, sending, changing a setting, approving) needs explicit operator confirmation, obtained by the orchestrator through its question channel before the step runs. Never infer consent from the task text. Treat every exec run as state-changing, because an agent-driven run can click, type, and submit.
  5. Install. Never install Aside and never run install tooling for it. If the operator wants Aside's own browser skill added to their coding agents, advise the operator to run aside skills install; the orchestrator does not run it.
  6. Secrets. The session carries the operator's logins, so never place credentials, cookies, tokens, or session data in any output, log, file, report, or prompt. Cite screenshots by path and carry only the minimum page text a step needs.
  7. Output size. Redirect verbose REPL output to a file and bring only the exit code and a bounded tail into context.

Optional registration

Aside is never part of the default configuration. An operator who wants the MCP server registers it with one explicit command:

moai mcp add aside --command aside --args mcp --scope user

Omit --scope user to register it for one project instead. The registration is optional and never a prerequisite of any workflow in this skill.

Relation to /moai e2e

/moai e2e --tool aside is the only way Aside enters the e2e workflow: it is explicit-only, never auto-detected, never offered, and never recommended. The orchestrator loads this skill first and runs every Aside step itself. When Aside is absent, fails its availability probe (aside --version), is signed out, or is excluded (for example when CI=true), the workflow continues silently on the platform default toolchain, with no Aside-specific message, prompt, install attempt, or failure.

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.