oh-my-agent 11.11.1 → 12.0.1

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.
Files changed (3) hide show
  1. package/README.md +6 -12
  2. package/bin/cli.js +819 -821
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -10,6 +10,10 @@ Spawning parallel agents is the easy part. The hard part is knowing whether they
10
10
 
11
11
  oh-my-agent makes the claim falsifiable. A Stop hook refuses to end your session until your project's own `typecheck` / `test` / `lint` script exits 0. A gate command decides whether a workflow really ran by looking for the artifacts it must have left behind — and its JSON verdict, not the agent's summary, is the result. An independent judge with a fresh context re-verifies every criterion each round, including the ones that already passed. Every gate decision lands on an append-only event log you can read after the fact. Then it runs that same discipline across a dozen agent runtimes from one portable `.agents/` directory.
12
12
 
13
+ ![oh-my-agent explainer](https://github.com/first-fluke/oh-my-agent/raw/main/docs/assets/video/oh-my-agent-explainer.gif)
14
+
15
+ [Watch the full video (35s)](https://github.com/first-fluke/oh-my-agent/blob/main/docs/assets/video/oh-my-agent-explainer.mp4)
16
+
13
17
  ## Verification, Not Narration
14
18
 
15
19
  Each mechanism below is mechanical: a command exits 0 or it doesn't, a file is on disk or it isn't. No LLM is asked whether the work "looks correct."
@@ -44,18 +48,8 @@ irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.p
44
48
  bunx oh-my-agent@latest
45
49
  ```
46
50
 
47
- ### Install as an Agent Plugin
48
-
49
- oma exports a portable [Agent Plugins](https://agent-plugins.org) 1.0.0 package — the open packaging standard backed by AWS, Cursor, Microsoft, OpenAI, and Vercel:
50
-
51
- ```bash
52
- oma emit --target agent-plugin # writes generated/agent-plugin/
53
- ```
54
-
55
- Point any conformant client (Kiro, AWS Agent Toolkit, and more as clients roll out support) at that directory. Conformant clients load the skills and MCP servers; workflows, rules, and `oma-config.yaml` ride along under the `com.firstfluke.oma` extension namespace for oma-aware installs. Hooks and `oma agent:spawn` still need the full `bunx oh-my-agent@latest` install.
56
-
57
51
  <details>
58
- <summary>Or install skills with Microsoft's <a href="https://github.com/microsoft/apm">Agent Package Manager</a> (APM), a package manager for the same ecosystem. Click to expand.</summary>
52
+ <summary>Or install skills with Microsoft's <a href="https://github.com/microsoft/apm">Agent Package Manager</a> (APM). Click to expand.</summary>
59
53
 
60
54
  > Not to be confused with `oma-observability`'s APM (Application Performance Monitoring).
61
55
 
@@ -68,7 +62,7 @@ apm install first-fluke/oh-my-agent
68
62
  apm install first-fluke/oh-my-agent/.agents/skills/oma-frontend
69
63
  ```
70
64
 
71
- Agent Plugins is the package format; APM is an installer that ships skills only. For workflows, rules, `oma-config.yaml`, keyword-detection hooks, and the `oma agent:spawn` CLI, use `bunx oh-my-agent@latest`. Pick one distribution per project to avoid drift.
65
+ APM ships skills only. For workflows, rules, `oma-config.yaml`, keyword-detection hooks, and the `oma agent:spawn` CLI, use `bunx oh-my-agent@latest`. Pick one distribution per project to avoid drift.
72
66
 
73
67
  </details>
74
68