burhan-mop 0.1.3 → 0.1.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.MOP/scripts/mop-core.mjs +5 -0
- package/AGENTS.md +9 -0
- package/README.bm.md +1 -1
- package/README.md +1 -1
- package/package.json +1 -1
|
@@ -193,6 +193,11 @@ const routeRules = [
|
|
|
193
193
|
support: ['tester', 'reviewer'],
|
|
194
194
|
keywords: ['code', 'coding', 'implement', 'buat file', 'ubah file', 'fix code', 'script', 'function']
|
|
195
195
|
},
|
|
196
|
+
{
|
|
197
|
+
role: 'browser',
|
|
198
|
+
support: ['researcher', 'tester'],
|
|
199
|
+
keywords: ['browser', 'browse', 'scrape', 'scraping', 'extract', 'click', 'login flow', 'fill form', 'captcha', 'bot detection', 'website', 'url', 'webpage']
|
|
200
|
+
},
|
|
196
201
|
{
|
|
197
202
|
role: 'researcher',
|
|
198
203
|
support: ['planner'],
|
package/AGENTS.md
CHANGED
|
@@ -14,8 +14,17 @@ follow `.MOP/PROTOCOL.md`.
|
|
|
14
14
|
It selects one primary role and may recommend any number of support roles
|
|
15
15
|
when genuinely needed. If no named agent exists for a needed role, ask the
|
|
16
16
|
user to name it and save it with `agent activate`.
|
|
17
|
+
|
|
18
|
+
| Role | Name | Description |
|
|
19
|
+
| :--- | :--- | :--- |
|
|
20
|
+
| **[qa]** | QA Engineer | Test plans, coverage gaps, regression |
|
|
21
|
+
| **[ai]** | Prompt Alchemist | Prompt engineering, AI tuning, LLM evaluation |
|
|
22
|
+
| **[seo]** | SEO Strategist | Technical SEO, on-page, audits, implementation specs |
|
|
23
|
+
| **[browser]** | Browsing Agent | Web browsing, scraping, form filling, bot bypass, extraction |
|
|
24
|
+
|
|
17
25
|
- If the router marks the task as ambiguous, the named primary agent must ask
|
|
18
26
|
clarifying questions before implementation.
|
|
27
|
+
- **[browser] Agent Rule**: Before creating a new browser session with `browser-act`, you must check the user's default browser (e.g., using `xdg-settings get default-web-browser` on Linux) or ask them what browser they use (Chrome, Edge, Brave, Opera). If they use something other than the built-in Chrome, use `browser-act`'s `chrome-direct` mode and guide them to start their browser with remote debugging (`--remote-debugging-port`), rather than just creating a default `chrome` browser.
|
|
19
28
|
- If the router returns `partyMode.active: true`, use Party Mode. Show
|
|
20
29
|
`PARTY MODE` in large uppercase before the dialogue, then generate the
|
|
21
30
|
agent-to-agent and agent-to-user dialogue explicitly in your response using this exact format:
|
package/README.bm.md
CHANGED
|
@@ -142,7 +142,7 @@ dan merge hanya bila workflow selamat.
|
|
|
142
142
|
| --- | --- |
|
|
143
143
|
| npm package | [`burhan-mop`](https://www.npmjs.com/package/burhan-mop) |
|
|
144
144
|
| command latest | `npx burhan-mop install` |
|
|
145
|
-
| GitHub release | [`v0.1.
|
|
145
|
+
| GitHub release | [`v0.1.4`](https://github.com/BURHANDEV-ENTERPRISE/BURHAN-MOP/releases/tag/v0.1.4) |
|
|
146
146
|
| Node | `>=20` |
|
|
147
147
|
|
|
148
148
|
## Links
|
package/README.md
CHANGED
|
@@ -141,7 +141,7 @@ and merges only when the workflow is safe.
|
|
|
141
141
|
| --- | --- |
|
|
142
142
|
| npm package | [`burhan-mop`](https://www.npmjs.com/package/burhan-mop) |
|
|
143
143
|
| latest command | `npx burhan-mop install` |
|
|
144
|
-
| GitHub release | [`v0.1.
|
|
144
|
+
| GitHub release | [`v0.1.4`](https://github.com/BURHANDEV-ENTERPRISE/BURHAN-MOP/releases/tag/v0.1.4) |
|
|
145
145
|
| Node | `>=20` |
|
|
146
146
|
|
|
147
147
|
## Links
|