Define the job
Name the user, workflow surface, inputs, saved state, output, and one clear measure of success.
Describe the focused app you want inside Moxby. Get a build-ready Mod plan with local state, interface states, data flow, permissions, and acceptance criteria.
Mods are apps that run inside your browser through Moxby. The planner turns a rough idea into a product contract for the app itself, including what it reads, what it stores locally, how it connects to the active page, and how a user knows it worked.
Create an SEO review Mod that works beside the current page.
01Surface: a focused local browser app launched from the Mods tab
02Inputs: current URL, page content selected by the user, target query, and optional comparison pages
03Local state: saved reviews, evidence links, priorities, and revision history
04Actions: analyze the current page, compare supplied evidence, and export a review-ready brief
05Acceptance: every finding links to visible evidence and the Mod works without a separate SaaS dashboard
Name the user, workflow surface, inputs, saved state, output, and one clear measure of success.
Receive the interface states, page-context handoff, local storage plan, permissions, errors, and acceptance criteria.
Create the first version, run it in the browser, and keep refining the Mod against the real workflow.
These tools give value before installation and connect the finished plan to the Moxby browser capability built to run it.
Yes. A Mod can add capabilities to an existing website or run as a focused app of its own inside Moxby.
Yes. The plan can define which page context is passed into the Mod and what the user must explicitly approve.
No. It creates the build prompt and product contract. Moxby Chat builds and refines the Mod.
Yes. A Mod can provide the operating surface or evidence a Mission uses while the Mission measures and improves toward its KPI.
Chat on any page, build Mods, run Missions, and add ready-made products from the Marketplace.