awesome-agents 0.1.3 → 0.1.6

package/AGENTS.md

@@ -9,10 +9,11 @@ OpenCode.
 
 The canonical source format is repo-neutral:
 
-- `agents/profiles/*.agent.yaml`: preferred YAML profile definitions.
-- `agents/profiles/*.agf.yaml`: Agent Format-style YAML profile definitions.
-- `agents/profiles/*.md`: Markdown profile definitions with YAML frontmatter.
-- `agents/adapters/<harness>/*`: optional harness-specific metadata and notes.
+- `agents/<slug>/agent.yaml`: preferred YAML profile definition.
+- `agents/<slug>/agent.agf.yaml`: Agent Format-style YAML profile definition.
+- `agents/<slug>/agent.md`: Markdown profile definition with YAML frontmatter.
+- `agents/<slug>/scripts/`: agent-owned scripts installed into the agent home.
+- `agents/<slug>/references/`: agent-owned references installed into the agent home.
 
 Never hard-code a particular source repository into runtime behavior, tests, or
 examples. Use neutral fixture/source names unless a test is explicitly about
@@ -53,6 +54,8 @@ source resolution.
 ## Safety
 
 - Never overwrite or delete unmanaged harness files by default.
+- Install agent-owned support files into `~/.agents/homes/<slug>/`, not into
+  harness configuration directories.
 - Keep install behavior deterministic and noninteractive. `--yes` exists for
   parity with `npx skills`, but the CLI should not require prompts to complete.
 - Do not mutate harness configuration beyond writing the selected generated

package/CHANGELOG.md

@@ -2,6 +2,39 @@
 
 This file is maintained by `npm run changelog` and `npm run release`. Release entries are generated from git commit history.
 
+## 0.1.6 - 2026-07-06
+
+Changes since `v0.1.5`.
+
+### Changed
+
+- Align harness detection docs (70a1f8e)
+- Improve agent install workflow (61470fc)
+
+## 0.1.5 - 2026-07-06
+
+Changes since `v0.1.4`.
+
+- No commits found for this release.
+
+## 0.1.4 - 2026-07-06
+
+Changes since `v0.1.3`.
+
+### Added
+
+- Add justfile for lint/test/release/publish workflows (7fe04ba)
+- Add agent detail page and visual treatment explorations (7d29557)
+- Add Claude Code plugin for browsing and installing agent profiles (5a11e6f)
+- Add awesome-agents.com marketing/directory site (9ce50cd)
+
+### Changed
+
+- Link leaderboard rows to per-agent pages (6f2c471)
+- Default install to every detected harness on PATH (b5af687)
+- Render Codex profile metadata as comments (59395cc)
+- Install agent-owned support files (3ede3ce)
+
 ## 0.1.3 - 2026-07-05
 
 Initial tracked release.
@@ -31,6 +64,8 @@ Initial tracked release.
 - Replace source-specific help and documentation examples with neutral `owner/repo` examples.
 - Parse repo-neutral YAML profile files in addition to Markdown frontmatter files.
 - Replace source-specific test fixtures with neutral profile-source fixtures.
+- Prefer `agents/<slug>/agent.yaml` source directories and install colocated
+  `scripts/` and `references/` into the agent home.
 
 ## 0.1.1 - 2026-07-05
 

package/README.md

@@ -6,8 +6,8 @@ agent profile instead of a skill.
 
 Supported sources are GitHub repos, Git URLs, or local checkouts that use the
 agent-profile source layout. Profiles are read from YAML or Markdown files under
-`agents/profiles/`, adapted for the selected harness, and installed into the
-right place for Codex, Claude Code, or OpenCode.
+`agents/<slug>/`, adapted for the selected harness, and installed into the
+right place for Codex, Claude Code, OpenCode, or tenex-edge.
 
 ## Install And Run
 
@@ -15,7 +15,7 @@ Use the CLI with `npx`:
 
 ```bash
 npx awesome-agents add owner/repo --agent triage-agent
-npx awesome-agents add owner/repo --agent triage-agent --harness opencode
+npx awesome-agents add owner/repo --agent triage-agent --harness tenex-edge
 ```
 
 From this repo during development:
@@ -43,17 +43,25 @@ Useful install options:
 - `--agent <slug>` to select an agent profile, for example `--agent triage-agent`
 - `--profile <slug>` or `--skill <slug>` as explicit profile aliases; `--skill`
   is command-shape compatibility and does not mean the artifact is a skill
-- `--harness codex|claude-code|opencode|*` to select target harnesses
+- omit a profile selector in an interactive terminal to choose source profiles
+  from a checkbox list; every profile is selected by default
+- `--yes` to accept detected profile and harness selections without opening selectors
+- `--harness codex|claude-code|opencode|tenex-edge|*` to select target harnesses;
+  without it, the CLI detects harness CLIs on `PATH`; interactive multi-detect
+  opens a checkbox selector with every detected harness selected, and
+  noninteractive installs use every detected harness. If none are detected, pass
+  `--harness`.
 - `--all` to install all profiles to all supported harnesses
 - `--dry-run` to preview writes
-- `--project` for project-level install where supported; Codex profiles install globally
+- `--project` for project-level install where supported; Codex and tenex-edge install globally
 - `--global` for user-level install
 - `--list` to inspect available source profiles without installing
 
 Human-readable output uses subtle ANSI color. Set `NO_COLOR=1` to disable color,
-or pass `--json` for machine-readable output. After an install, the CLI also
-prints run commands for target harness CLIs it finds on `PATH`, such as
-`codex --profile <profile>` or `claude --agent <profile>`.
+or pass `--json` for machine-readable output. After an install, the CLI groups
+run commands by profile for target harness CLIs it finds on `PATH`, such as
+`codex --profile <profile>`, `claude --agent <profile>`, or
+`tenex-edge launch <profile>`.
 
 ## Harness Targets
 
@@ -62,12 +70,14 @@ Project installs write to:
 - Codex: not supported; Codex profiles load from user config
 - Claude Code: `.claude/agents/<profile>.md`
 - OpenCode: `.opencode/agents/<profile>.md`
+- tenex-edge: not supported; tenex-edge agents are machine-local
 
 Global installs write to:
 
 - Codex: `$CODEX_HOME/<profile>.config.toml`, or `~/.codex/<profile>.config.toml`
 - Claude Code: `$CLAUDE_HOME/agents/<profile>.md`, or `~/.claude/agents/<profile>.md`
 - OpenCode: `$OPENCODE_CONFIG_DIR/agents/<profile>.md`, or `~/.config/opencode/agents/<profile>.md`
+- tenex-edge: `$TENEX_EDGE_HOME/agents/<profile>.json`, or `~/.tenex-edge/agents/<profile>.json`
 
 The CLI keeps its own registry at `.awesome-agents/installed.json` for project
 installs or `~/.awesome-agents/installed.json` for global installs. `list`,
@@ -89,19 +99,36 @@ An agent-profile source should look like:
 
 ```text
 agents/
-  profiles/
-    triage-agent.agent.yaml
-    ops-agent.agf.yaml
-    legacy-agent.md
-  adapters/
-    codex/
-      optional-agent.md
+  triage-agent/
+    agent.yaml
+  ops-agent/
+    agent.agf.yaml
+    skills/
+      gh-pages-publisher/
+        SKILL.md
+    scripts/
+      heartbeat.sh
+    references/
+      runbook.md
 ```
 
 YAML profile files are preferred. The loader also accepts Markdown files with
 YAML frontmatter for compatibility with tools that use `.agent.md`-style
-profiles. Adapters are optional and can provide harness-specific metadata, but a
-profile should stand on its own without requiring an adapter.
+profiles. Agent-owned `scripts/` and `references/` are installed into
+`~/.agents/homes/<slug>/scripts` and `~/.agents/homes/<slug>/references`.
+Profiles may also declare immediately relevant skills:
+
+```yaml
+skills:
+  - gh-pages-publisher
+  - pablof7z/tenex-edge basic-skill
+```
+
+Bare skill names are resolved from the profile directory, then the source
+checkout, then `~/.agents/skills`. Source-qualified entries use the same source
+plus skill selector shape as `npx skills add <source> --skill <skill>`.
+Declared skills are copied into `~/.agents/homes/<slug>/skills/<skill>` and
+listed with complete paths in the installed agent prompt.
 
 ## Examples
 
@@ -109,6 +136,7 @@ profile should stand on its own without requiring an adapter.
 npx awesome-agents add owner/repo --list
 npx awesome-agents add owner/repo --agent triage-agent
 npx awesome-agents add owner/repo --agent triage-agent --harness codex --global
+npx awesome-agents add owner/repo --agent triage-agent --harness tenex-edge
 npx awesome-agents add owner/repo --all --dry-run
 npx awesome-agents use owner/repo --agent triage-agent --harness claude-code
 npx awesome-agents list --json

package/docs/cli.md

@@ -10,11 +10,16 @@
 - `update` / `upgrade` reinstalls from the recorded source.
 - `init` creates a profile source skeleton.
 
-The CLI is noninteractive for the initial scaffold. Options such as `--yes` are
-accepted for parity, but command behavior should be fully scriptable. Installs
-default to project scope where the selected harness supports project-local
-profiles. Codex is the exception: Codex `--profile` loads named config layers
-from `CODEX_HOME`, so Codex profile installs are user-level.
+The CLI stays scriptable by default. In an interactive terminal, `add` opens a
+checkbox selector when no profile selector is provided; every source profile is
+selected by default. When no target harness is provided, `add` detects supported
+harness CLIs on `PATH`; multiple detected harnesses open a checkbox selector
+with every harness selected by default. Non-TTY runs, `--json`, and `--yes` use
+all detected selections without prompting. Installs default to project scope
+where the selected harness supports project-local profiles. Codex and tenex-edge
+are exceptions: Codex `--profile` loads named config layers from `CODEX_HOME`,
+while tenex-edge agents live in its machine keystore under
+`$TENEX_EDGE_HOME/agents/` or `~/.tenex-edge/agents/`.
 
 ## Source Resolution
 
@@ -25,7 +30,7 @@ Supported source values:
 - GitHub URL: `https://github.com/owner/repo`
 
 For GitHub sources, the CLI clones a shallow temporary copy and reads
-`agents/profiles`.
+`agents/<slug>/agent.yaml` style definitions.
 
 There is no default source. `add`, `install`, and `use` require the caller to
 provide a source explicitly.
@@ -51,18 +56,34 @@ generated profile is installed:
 npx awesome-agents add owner/repo --agent triage-agent --harness opencode
 ```
 
-For backward compatibility, `--agent codex`, `--agent claude-code`, and
-`--agent opencode` are still accepted as harness selectors.
+For backward compatibility, `--agent codex`, `--agent claude-code`,
+`--agent opencode`, and `--agent tenex-edge` are still accepted as harness
+selectors.
+
+When no harness selector is provided, `add` detects `codex`, `claude`,
+`opencode`, and `tenex-edge` on `PATH`. If none are found, the command fails and
+asks for `--harness`.
+
+When no profile selector is provided in an interactive terminal, `add` prompts
+with a checkbox list of source profiles and their summaries. Pressing Enter
+accepts the default of installing every listed profile. Scripts can use `--yes`,
+`--json`, or a non-TTY stdin/stdout path to keep the same noninteractive default.
 
 The `--skill` flag is accepted only as a command-shape alias for `--profile`.
 Installed artifacts remain operational agent profiles.
 
+Profiles may still declare immediately relevant skills in their source
+definition. Those dependencies are copied into
+`~/.agents/homes/<profile>/skills/<skill>` and appended to the installed prompt
+with complete paths; this does not make the profile itself a skill.
+
 After install, human-readable output should show the CLI command to run each
 installed profile through any matching harness CLI found on `PATH`. Examples:
 
 ```bash
 codex --profile triage-agent
 claude --agent triage-agent
+tenex-edge launch triage-agent
 ```
 
 ## Install Safety

package/docs/product/README.md

@@ -11,7 +11,7 @@ unless the user confirms them.
 - `product-scope.md`: What `awesome-agents` is for and how it differs from skills.
 - `command-model.md`: Command shape, `npx skills` parity, defaults, and scriptability.
 - `profile-source-format.md`: Source repositories, canonical profiles, adapters, and install sources.
-- `harness-targets.md`: Codex, Claude Code, and OpenCode rendering/target behavior.
+- `harness-targets.md`: Codex, Claude Code, OpenCode, and tenex-edge rendering/target behavior.
 - `safety-and-publishing.md`: Install safety, registry behavior, verification, and npm/GitHub publish state.
 - `open-questions.md`: Unresolved product questions.
 

package/docs/product/command-model.md

@@ -24,9 +24,9 @@ The CLI supports:
   language such as `npx awesome-agents add owner/repo --agent triage-agent`.
 - `--profile <slug>` to select profiles explicitly.
 - `--skill <slug>` as a compatibility alias, even though the artifact is a profile.
-- `--harness <codex|claude-code|opencode|*>` to select target harnesses.
-- `--agent <codex|claude-code|opencode|*>` remains accepted as a legacy harness
-  selector when the value is a known harness or harness alias.
+- `--harness <codex|claude-code|opencode|tenex-edge|*>` to select target harnesses.
+- `--agent <codex|claude-code|opencode|tenex-edge|*>` remains accepted as a
+  legacy harness selector when the value is a known harness or harness alias.
 - `--all` to install every profile.
 - `--list` to inspect source profiles before installing.
 
@@ -36,12 +36,17 @@ Accepted implementation decision:
 
 - Install scope defaults to project where the target harness supports project-local profiles.
 - Codex is an exception because `codex --profile <name>` loads
-  `$CODEX_HOME/<name>.config.toml`. Codex profile installs should use that
-  user-level config-layer target.
-- Codex is the default harness when no `--harness` or legacy harness-valued
-  `--agent` is provided.
-- The CLI is noninteractive in the initial scaffold.
-- `--yes` is accepted for command-shape parity, but prompts are not currently required.
+  `$CODEX_HOME/<name>.config.toml`. tenex-edge is also global because invitable
+  local agents live under `$TENEX_EDGE_HOME/agents/` or `~/.tenex-edge/agents/`.
+- When no `--harness` or legacy harness-valued `--agent` is provided, the CLI
+  detects supported harness CLIs on `PATH` (`codex`, `claude`, `opencode`, and
+  `tenex-edge`).
+- If one harness is detected, install to it. If multiple harnesses are detected,
+  interactive installs open a checkbox selector with every detected harness
+  selected by default; noninteractive, `--json`, and `--yes` installs use every
+  detected harness.
+- If no harness is detected, fail with a clear message asking for `--harness`.
+- `--harness <harness>` (or a harness-valued `--agent`) overrides detection.
 
 ## Scriptability
 

package/docs/product/harness-targets.md

@@ -9,6 +9,7 @@ Initial harness targets:
 - Codex
 - Claude Code
 - OpenCode
+- tenex-edge
 
 ## Codex
 
@@ -29,11 +30,12 @@ file from `CODEX_HOME`.
 
 The generated TOML includes:
 
-- `name`
-- `description`
 - optional model settings
 - `developer_instructions`
 
+Profile name and summary are emitted as comments, not TOML keys, because Codex
+rejects unknown configuration fields under strict config parsing.
+
 ## Claude Code
 
 Generated Claude Code subagents install to:
@@ -52,8 +54,29 @@ Generated OpenCode agents install to:
 
 OpenCode output is Markdown with frontmatter and a generated marker.
 
+## tenex-edge
+
+Generated tenex-edge agents install to:
+
+- Project: not supported; tenex-edge agents are machine-local
+- Global: `$TENEX_EDGE_HOME/agents/<profile>.json`, or `~/.tenex-edge/agents/<profile>.json`
+
+Run with:
+
+```bash
+tenex-edge launch <profile>
+```
+
+The generated JSON is a tenex-edge local agent keystore entry with:
+
+- a generated Nostr keypair, preserved across reinstalls
+- `command: ["claude"]`
+- an inline Claude `agent` definition passed by tenex-edge as `--agents`
+- a byline derived from the profile summary
+
 ## Adapter Gaps
 
 Some source repositories may provide Codex adapters first. Claude Code and
 OpenCode use generated defaults unless a source repository adds native adapters
-for those harnesses.
+for those harnesses. tenex-edge uses a native adapter when present, otherwise it
+reuses the Claude Code adapter before falling back to the base profile.

package/docs/product/product-scope.md

@@ -8,8 +8,8 @@ These notes capture what `awesome-agents` is and why it exists.
 - It should be installable with `npx`.
 - Its command structure should mirror `npx skills`, but for agent profiles.
 - It should install profiles from any explicit source repository that follows
-  the `agents/profiles` source layout.
-- Initial harness targets are Codex, Claude Code, and OpenCode.
+  the `agents/<slug>/agent.yaml` source layout.
+- Harness targets are Codex, Claude Code, OpenCode, and tenex-edge.
 - The package should be published after the scaffold works.
 
 ## Product Boundary
@@ -40,3 +40,8 @@ Product correction:
   the artifact shape and target harnesses.
 - Examples and tests should use neutral source names unless they are testing
   source resolution itself.
+- Source repositories should use one agent definition format per agent directory:
+  `agents/<slug>/agent.yaml` plus colocated support material.
+- `awesome-agents` installs local support material and declared immediately
+  relevant skills into `~/.agents/homes/<slug>/` and transcribes the agent
+  definition to the target harness.

package/docs/product/profile-source-format.md

@@ -8,27 +8,40 @@ The source format is intentionally repo-neutral:
 
 ```text
 agents/
-  profiles/
-    <profile>.agent.yaml
-    <profile>.agf.yaml
-    <profile>.md
-  adapters/
-    <harness>/
-      <profile>.md
+  <profile>/
+    agent.yaml
+    skills/
+    scripts/
+    references/
 ```
 
 Canonical profiles live at:
 
 ```text
-agents/profiles/*.{agent.yaml,agent.yml,agf.yaml,agf.yml,yaml,yml,agent.md,md}
+agents/<profile>/{agent.yaml,agent.yml,agent.agf.yaml,agent.agf.yml,agent.md}
 ```
 
-Optional harness adapters live at:
+Optional agent-owned support material lives at:
 
 ```text
-agents/adapters/<harness>/*
+agents/<profile>/scripts/*
+agents/<profile>/references/*
 ```
 
+Immediately relevant skills can be declared in the profile definition:
+
+```yaml
+skills:
+  - gh-pages-publisher
+  - pablof7z/tenex-edge basic-skill
+```
+
+Bare skill names resolve from the profile directory, then the source checkout,
+then from `~/.agents/skills`. Source-qualified entries use the same source plus
+skill selector shape as `npx skills add <source> --skill <skill>`. Installed
+skills are copied into `~/.agents/homes/<profile>/skills/<skill>` and appended
+to the rendered agent prompt with complete paths.
+
 ## Profile Files
 
 YAML profile files are preferred. The loader should support a pragmatic subset
@@ -42,8 +55,11 @@ of emerging YAML agent-definition shapes:
 
 The CLI should preserve canonical profile content and generate harness-specific install files. A profile is reusable product content, not local machine setup.
 
-Adapters are optional. A profile should be useful without a harness adapter; an
-adapter is only an override for harness-specific metadata or instructions.
+Agent-owned scripts and references should be installed into
+`~/.agents/homes/<profile>/scripts` and
+`~/.agents/homes/<profile>/references`.
+Declared skills should be installed into
+`~/.agents/homes/<profile>/skills/<skill>`.
 
 Profile source files are intentionally under `agents/`, not `skills/`, because
 the source format models agent profiles separately from loadable skills.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "awesome-agents",
-  "version": "0.1.3",
-  "description": "Install reusable agent profiles into Codex, Claude Code, and OpenCode.",
+  "version": "0.1.6",
+  "description": "Install reusable agent profiles into Codex, Claude Code, OpenCode, and tenex-edge.",
   "type": "module",
   "bin": {
     "awesome-agents": "bin/awesome-agents.js"
@@ -43,6 +43,7 @@
     "node": ">=22.12.0"
   },
   "dependencies": {
+    "@inquirer/checkbox": "^4.3.2",
     "commander": "^15.0.0",
     "yaml": "^2.9.0"
   }