hermes-github-app-plugin 0.1.0__tar.gz

hermes_github_app_plugin-0.1.0/.github/workflows/cd.yaml

@@ -0,0 +1,83 @@
+name: CD
+
+on:
+  push:
+    tags:
+      - '*'
+
+permissions:
+  contents: read
+
+jobs:
+  validate-tag:
+    name: Validate release tag
+    runs-on: ubuntu-latest
+    outputs:
+      release_tag: ${{ steps.validate.outputs.release_tag }}
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+      - name: Validate tag and package version
+        id: validate
+        run: |
+          python - <<'PY'
+          import os
+          import re
+          import tomllib
+          from pathlib import Path
+
+          tag = os.environ["GITHUB_REF_NAME"]
+          version = tomllib.loads(Path("pyproject.toml").read_text())["project"]["version"]
+          is_release = re.fullmatch(r"[0-9]+\.[0-9]+\.[0-9]+", tag) is not None
+          with open(os.environ["GITHUB_OUTPUT"], "a", encoding="utf-8") as output:
+              print(f"release_tag={str(is_release).lower()}", file=output)
+          if not is_release:
+              print(f"Tag {tag!r} is not a PyPI release tag; skipping publish.")
+              raise SystemExit(0)
+          if version != tag:
+              raise SystemExit(f"pyproject version {version!r} does not match tag {tag!r}")
+          print(f"Release version verified: {version}")
+          PY
+
+  build:
+    name: Build distribution
+    needs: validate-tag
+    if: needs.validate-tag.outputs.release_tag == 'true'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+          cache: pip
+      - name: Install build tools
+        run: python -m pip install build twine
+      - name: Build package
+        run: python -m build
+      - name: Check distribution metadata
+        run: python -m twine check dist/*
+      - name: Upload distribution artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: python-distribution
+          path: dist/*
+          if-no-files-found: error
+
+  publish-pypi:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - name: Download distribution artifact
+        uses: actions/download-artifact@v4
+        with:
+          name: python-distribution
+          path: dist
+      - name: Publish package distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

hermes_github_app_plugin-0.1.0/.github/workflows/ci.yaml

@@ -0,0 +1,31 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+jobs:
+  lint-static-test:
+    name: Lint, static analysis, and tests
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+      - name: Install package
+        run: python -m pip install -e '.[dev]'
+      - name: Ruff format check
+        run: ruff format --check .
+      - name: Ruff lint
+        run: ruff check .
+      - name: Mypy
+        run: mypy
+      - name: Pytest
+        run: pytest

hermes_github_app_plugin-0.1.0/.gitignore

@@ -0,0 +1,9 @@
+.coverage
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+__pycache__/
+*.egg-info/
+dist/
+build/
+.venv/

hermes_github_app_plugin-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Hermes GitHub App Plugin Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

hermes_github_app_plugin-0.1.0/PKG-INFO

@@ -0,0 +1,149 @@
+Metadata-Version: 2.4
+Name: hermes-github-app-plugin
+Version: 0.1.0
+Summary: Hermes plugin for per-agent GitHub App identity, gh/git wrappers, and GitHub App-aware tools.
+Author: Hermes GitHub App Plugin Contributors
+License: MIT
+License-File: LICENSE
+Requires-Python: >=3.10
+Requires-Dist: httpx>=0.25
+Requires-Dist: pyjwt[crypto]>=2.8
+Requires-Dist: pyyaml>=6.0
+Provides-Extra: dev
+Requires-Dist: mypy>=1.8; extra == 'dev'
+Requires-Dist: pytest-cov>=5.0; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.8; extra == 'dev'
+Requires-Dist: types-pyyaml>=6.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Hermes GitHub App Plugin
+
+Hermes plugin for using **per-agent GitHub App identities** instead of a human `gh`/SSH identity.
+
+Each Hermes agent runs the same package but is configured with its own GitHub App:
+
+```yaml
+github_app:
+  client_id: "Iv1.exampleclientid"
+  installation_id: "987654"
+  private_key_path: "~/.hermes/secrets/agent-github-app.private-key.pem"
+  app_slug: "hermes-agent"
+```
+
+Environment variables with the same meaning are also supported:
+
+- `GITHUB_APP_CLIENT_ID`
+- `GITHUB_APP_INSTALLATION_ID`
+- `GITHUB_APP_PRIVATE_KEY_PATH`
+- `GITHUB_APP_PRIVATE_KEY` (PEM contents; useful for CI)
+
+Repository access is controlled by the GitHub App installation scope in GitHub. If an agent should not access a repository, remove that repository from the GitHub App installation scope.
+
+## Client ID vs. installation ID
+
+`client_id` identifies the GitHub App registration. GitHub recommends using the GitHub App **client ID** as the JWT `iss` claim when authenticating as an app.
+
+`installation_id` identifies one installation of that app on a specific user or organization account. It is required when exchanging the app JWT for an installation access token via `POST /app/installations/{installation_id}/access_tokens`.
+
+In other words: `client_id` answers "which GitHub App is signing this JWT?" while `installation_id` answers "which installed copy of that app should this token act as?" The same GitHub App can have multiple installation IDs if it is installed on multiple accounts.
+
+## Install
+
+```bash
+pip install hermes-github-app-plugin
+hermes plugins enable github-app
+hermes-github-app setup
+hermes-github-app doctor --repo OWNER/REPO
+```
+
+`setup` walks through the required values one by one. Optional prompts are explicitly marked with `(optional)`:
+
+```text
+GitHub App client ID:
+GitHub App installation ID:
+GitHub App private key path:
+GitHub App slug (optional):
+```
+
+For scripted installs, pass flags and skip the network verification until secrets are mounted:
+
+```bash
+hermes-github-app setup --non-interactive --skip-verify \
+  --client-id Iv1.exampleclientid \
+  --installation-id 987654 \
+  --private-key-path ~/.hermes/secrets/agent-github-app.private-key.pem \
+  --app-slug hermes-agent
+```
+
+`doctor` checks local installation state and, unless `--skip-network` is set, verifies that an installation token can be minted and the optional repository probe is reachable.
+
+## CLI and wrappers
+
+```bash
+hermes-github-app setup
+hermes-github-app doctor --repo OWNER/REPO
+hermes-github-app status
+hermes-github-app token --repo OWNER/REPO
+hermes-github-app api --repo OWNER/REPO /repos/OWNER/REPO
+
+gh-app --repo OWNER/REPO pr list -R OWNER/REPO
+git-app --repo OWNER/REPO push origin my-branch
+```
+
+`gh-app` injects an ephemeral installation token as `GH_TOKEN` and `GITHUB_TOKEN` for the child `gh` process.
+`git-app` injects a temporary askpass helper so HTTPS Git operations authenticate as the GitHub App installation token without writing credentials into the remote URL.
+
+## Migrating existing Hermes skills and jobs
+
+To keep agents from falling back to local human credentials, update existing GitHub-related Hermes skills, cron jobs, and subagent prompts with these rules:
+
+- Use `github_app_*` tools for GitHub API operations when possible.
+- Replace authenticated `gh ...` examples with `gh-app --repo OWNER/REPO -- ...`.
+- Replace `git push` examples with `git-app --repo OWNER/REPO -- push ...`, or another HTTPS credential-helper flow backed by a freshly minted installation token.
+- Do not use `gh auth status` as proof of write identity; it reports local `gh` credentials and may show a human account.
+- Avoid SSH remotes for bot-managed worktrees. SSH uses local SSH keys, not the GitHub App token.
+- Add a pre-write check with `github_app_verify_identity` or `hermes-github-app status --repo OWNER/REPO`.
+- Avoid `@me` assumptions because the GitHub App bot is not the human operator.
+- Require write summaries to include the returned `auth_mode`, `app_slug`, `installation_id`, repository, operation, and URL/path.
+
+## Releasing to PyPI
+
+The package is built with Hatchling and publishes through the `CD` GitHub Actions workflow using PyPI Trusted Publishing / OIDC. The workflow listens to all pushed tags but only builds and publishes when the tag matches:
+
+```text
+^[0-9]+\.[0-9]+\.[0-9]+$
+```
+
+The tag must also match `project.version` in `pyproject.toml`.
+
+Before the first release, configure PyPI Trusted Publishing for this repository and workflow:
+
+- PyPI project name: `hermes-github-app-plugin`
+- Owner/repository: this GitHub repository
+- Workflow name: `cd.yaml`
+- Environment name: `pypi`
+
+Release example:
+
+```bash
+git tag 0.1.0
+git push origin 0.1.0
+```
+
+Tags like `v0.1.0`, `0.1`, or `0.1.0rc1` will not publish.
+
+## Hermes tools
+
+The plugin registers these tools:
+
+- `github_app_status`
+- `github_app_verify_identity`
+- `github_app_api`
+- `github_app_graphql`
+- `github_app_create_issue`
+- `github_app_comment_issue`
+- `github_app_create_pr`
+- `github_app_comment_pr`
+
+All mutating tools return auth metadata showing App mode, installation ID, app slug, and target repository.

hermes_github_app_plugin-0.1.0/README.md

@@ -0,0 +1,130 @@
+# Hermes GitHub App Plugin
+
+Hermes plugin for using **per-agent GitHub App identities** instead of a human `gh`/SSH identity.
+
+Each Hermes agent runs the same package but is configured with its own GitHub App:
+
+```yaml
+github_app:
+  client_id: "Iv1.exampleclientid"
+  installation_id: "987654"
+  private_key_path: "~/.hermes/secrets/agent-github-app.private-key.pem"
+  app_slug: "hermes-agent"
+```
+
+Environment variables with the same meaning are also supported:
+
+- `GITHUB_APP_CLIENT_ID`
+- `GITHUB_APP_INSTALLATION_ID`
+- `GITHUB_APP_PRIVATE_KEY_PATH`
+- `GITHUB_APP_PRIVATE_KEY` (PEM contents; useful for CI)
+
+Repository access is controlled by the GitHub App installation scope in GitHub. If an agent should not access a repository, remove that repository from the GitHub App installation scope.
+
+## Client ID vs. installation ID
+
+`client_id` identifies the GitHub App registration. GitHub recommends using the GitHub App **client ID** as the JWT `iss` claim when authenticating as an app.
+
+`installation_id` identifies one installation of that app on a specific user or organization account. It is required when exchanging the app JWT for an installation access token via `POST /app/installations/{installation_id}/access_tokens`.
+
+In other words: `client_id` answers "which GitHub App is signing this JWT?" while `installation_id` answers "which installed copy of that app should this token act as?" The same GitHub App can have multiple installation IDs if it is installed on multiple accounts.
+
+## Install
+
+```bash
+pip install hermes-github-app-plugin
+hermes plugins enable github-app
+hermes-github-app setup
+hermes-github-app doctor --repo OWNER/REPO
+```
+
+`setup` walks through the required values one by one. Optional prompts are explicitly marked with `(optional)`:
+
+```text
+GitHub App client ID:
+GitHub App installation ID:
+GitHub App private key path:
+GitHub App slug (optional):
+```
+
+For scripted installs, pass flags and skip the network verification until secrets are mounted:
+
+```bash
+hermes-github-app setup --non-interactive --skip-verify \
+  --client-id Iv1.exampleclientid \
+  --installation-id 987654 \
+  --private-key-path ~/.hermes/secrets/agent-github-app.private-key.pem \
+  --app-slug hermes-agent
+```
+
+`doctor` checks local installation state and, unless `--skip-network` is set, verifies that an installation token can be minted and the optional repository probe is reachable.
+
+## CLI and wrappers
+
+```bash
+hermes-github-app setup
+hermes-github-app doctor --repo OWNER/REPO
+hermes-github-app status
+hermes-github-app token --repo OWNER/REPO
+hermes-github-app api --repo OWNER/REPO /repos/OWNER/REPO
+
+gh-app --repo OWNER/REPO pr list -R OWNER/REPO
+git-app --repo OWNER/REPO push origin my-branch
+```
+
+`gh-app` injects an ephemeral installation token as `GH_TOKEN` and `GITHUB_TOKEN` for the child `gh` process.
+`git-app` injects a temporary askpass helper so HTTPS Git operations authenticate as the GitHub App installation token without writing credentials into the remote URL.
+
+## Migrating existing Hermes skills and jobs
+
+To keep agents from falling back to local human credentials, update existing GitHub-related Hermes skills, cron jobs, and subagent prompts with these rules:
+
+- Use `github_app_*` tools for GitHub API operations when possible.
+- Replace authenticated `gh ...` examples with `gh-app --repo OWNER/REPO -- ...`.
+- Replace `git push` examples with `git-app --repo OWNER/REPO -- push ...`, or another HTTPS credential-helper flow backed by a freshly minted installation token.
+- Do not use `gh auth status` as proof of write identity; it reports local `gh` credentials and may show a human account.
+- Avoid SSH remotes for bot-managed worktrees. SSH uses local SSH keys, not the GitHub App token.
+- Add a pre-write check with `github_app_verify_identity` or `hermes-github-app status --repo OWNER/REPO`.
+- Avoid `@me` assumptions because the GitHub App bot is not the human operator.
+- Require write summaries to include the returned `auth_mode`, `app_slug`, `installation_id`, repository, operation, and URL/path.
+
+## Releasing to PyPI
+
+The package is built with Hatchling and publishes through the `CD` GitHub Actions workflow using PyPI Trusted Publishing / OIDC. The workflow listens to all pushed tags but only builds and publishes when the tag matches:
+
+```text
+^[0-9]+\.[0-9]+\.[0-9]+$
+```
+
+The tag must also match `project.version` in `pyproject.toml`.
+
+Before the first release, configure PyPI Trusted Publishing for this repository and workflow:
+
+- PyPI project name: `hermes-github-app-plugin`
+- Owner/repository: this GitHub repository
+- Workflow name: `cd.yaml`
+- Environment name: `pypi`
+
+Release example:
+
+```bash
+git tag 0.1.0
+git push origin 0.1.0
+```
+
+Tags like `v0.1.0`, `0.1`, or `0.1.0rc1` will not publish.
+
+## Hermes tools
+
+The plugin registers these tools:
+
+- `github_app_status`
+- `github_app_verify_identity`
+- `github_app_api`
+- `github_app_graphql`
+- `github_app_create_issue`
+- `github_app_comment_issue`
+- `github_app_create_pr`
+- `github_app_comment_pr`
+
+All mutating tools return auth metadata showing App mode, installation ID, app slug, and target repository.

hermes_github_app_plugin-0.1.0/plugin.yaml

@@ -0,0 +1,27 @@
+name: github-app
+version: 0.1.0
+description: "GitHub App identity integration for Hermes: per-agent app token minting, GitHub API tools, gh/git wrappers, CLI, and workflow skill."
+author: Hermes GitHub App Plugin Contributors
+provides_tools:
+  - github_app_status
+  - github_app_verify_identity
+  - github_app_api
+  - github_app_graphql
+  - github_app_create_issue
+  - github_app_comment_issue
+  - github_app_create_pr
+  - github_app_comment_pr
+provides_cli:
+  - hermes-github-app
+  - gh-app
+  - git-app
+requires_env:
+  - name: GITHUB_APP_CLIENT_ID
+    description: "GitHub App client ID for this Hermes agent. Can also be set in ~/.hermes/config.yaml under github_app.client_id."
+    secret: false
+  - name: GITHUB_APP_INSTALLATION_ID
+    description: "GitHub App installation ID for this Hermes agent. Can also be set in ~/.hermes/config.yaml under github_app.installation_id."
+    secret: false
+  - name: GITHUB_APP_PRIVATE_KEY_PATH
+    description: "Path to the GitHub App private key PEM. Can also be set in ~/.hermes/config.yaml under github_app.private_key_path."
+    secret: true

hermes_github_app_plugin-0.1.0/pyproject.toml

@@ -0,0 +1,60 @@
+[build-system]
+requires = ["hatchling>=1.25"]
+build-backend = "hatchling.build"
+
+[project]
+name = "hermes-github-app-plugin"
+version = "0.1.0"
+description = "Hermes plugin for per-agent GitHub App identity, gh/git wrappers, and GitHub App-aware tools."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "MIT" }
+authors = [{ name = "Hermes GitHub App Plugin Contributors" }]
+dependencies = [
+  "httpx>=0.25",
+  "PyJWT[crypto]>=2.8",
+  "PyYAML>=6.0",
+]
+
+[project.optional-dependencies]
+dev = [
+  "mypy>=1.8",
+  "pytest>=8.0",
+  "pytest-cov>=5.0",
+  "ruff>=0.8",
+  "types-PyYAML>=6.0",
+]
+
+[project.entry-points."hermes_agent.plugins"]
+github-app = "hermes_github_app_plugin:register"
+
+[project.scripts]
+gh-app = "hermes_github_app_plugin.cli:gh_app_main"
+git-app = "hermes_github_app_plugin.cli:git_app_main"
+hermes-github-app = "hermes_github_app_plugin.cli:main"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/hermes_github_app_plugin"]
+
+[tool.hatch.build.targets.wheel.force-include]
+"plugin.yaml" = "hermes_github_app_plugin/plugin.yaml"
+
+[tool.ruff]
+line-length = 100
+target-version = "py310"
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "B", "UP", "SIM", "PL", "RUF"]
+ignore = ["PLR0913"]
+
+[tool.ruff.lint.per-file-ignores]
+"tests/**/*.py" = ["PLR2004"]
+
+[tool.mypy]
+python_version = "3.10"
+strict = true
+packages = ["hermes_github_app_plugin"]
+
+[tool.pytest.ini_options]
+addopts = "--cov=hermes_github_app_plugin --cov-report=term-missing"
+testpaths = ["tests"]

hermes_github_app_plugin-0.1.0/skills/github-app-workflow/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: github-app-workflow
+description: Use per-agent GitHub App identity for Hermes GitHub operations.
+version: 0.1.0
+author: Hermes GitHub App Plugin Contributors
+---
+
+# GitHub App Workflow
+
+Use this skill for GitHub operations from Hermes agents that are configured with a per-agent GitHub App.
+
+## First-time setup
+
+Run `hermes-github-app setup` to write `github_app` config into `~/.hermes/config.yaml`. The setup walkthrough marks optional values with `(optional)`; the required values are GitHub App client ID, installation ID, and private key path.
+
+After setup, run `hermes-github-app doctor --repo OWNER/REPO` to verify console scripts, config loading, private-key permissions, token minting, and repository access. Use `--skip-network` only for container/image builds where secrets or network access are not available yet.
+
+## Rules
+
+1. Prefer `github_app_*` plugin tools for GitHub API operations.
+2. Prefer `gh-app` over bare `gh` from the terminal.
+3. Prefer `git-app` or HTTPS/App-token credentials over SSH for GitHub writes.
+4. Do not rely on `gh auth status` as proof of the desired identity; it often reports the human account.
+5. Verify App mode before writes with `github_app_verify_identity` or `hermes-github-app status --repo OWNER/REPO`.
+6. Do not use `@me` assumptions; the actor is the app bot, not a human user.
+7. Expect comments, PRs, and API writes to appear as `<app-slug>[bot]`.
+8. Treat the GitHub App installation scope as the repository access boundary. The plugin does not maintain a separate local repository/owner allowlist.
+
+## Updating existing Hermes skills
+
+Patch any GitHub-related skill, cron prompt, or subagent instruction that mentions `gh`, `git push`, GitHub SSH remotes, or `@me` assumptions:
+
+- Replace bare `gh ...` examples with `gh-app --repo OWNER/REPO -- ...` when the command needs GitHub authentication.
+- Replace `git push` examples with `git-app --repo OWNER/REPO -- push ...`, or document an equivalent HTTPS credential-helper flow that uses a freshly minted installation token.
+- Add a pre-write verification step: `github_app_verify_identity` or `hermes-github-app status --repo OWNER/REPO`.
+- Do not treat `gh auth status` as proof of the write identity. It reports local `gh` credentials and may be a human account.
+- Remove or flag SSH remote examples for bot-managed worktrees. SSH uses local SSH keys, not the GitHub App installation token.
+- Replace `@me` queries with explicit usernames, teams, or repository-scoped queries because the app bot is not the human operator.
+- Require final write summaries to include `auth_mode`, `app_slug`, `installation_id`, `repository`, operation, and URL/path.
+
+For subagents, include the same rules in the delegated prompt because subagents run in separate sessions and may not inherit the parent agent's assumptions.
+
+## Verification
+
+Before reporting success for a write, include:
+
+- repository
+- operation
+- URL or API path
+- `auth_mode: github_app`
+- app slug if known
+- installation ID

hermes_github_app_plugin-0.1.0/src/hermes_github_app_plugin/__init__.py

@@ -0,0 +1,60 @@
+"""Hermes GitHub App plugin."""
+
+from __future__ import annotations
+
+from pathlib import Path
+
+from . import schemas, tools
+from .cli import main as cli_main
+from .cli import register_cli
+
+_TOOLSET = "github_app"
+_TOOLS = (
+    ("github_app_status", schemas.GITHUB_APP_STATUS, tools.github_app_status, "🤖"),
+    (
+        "github_app_verify_identity",
+        schemas.GITHUB_APP_VERIFY_IDENTITY,
+        tools.github_app_verify_identity,
+        "✅",
+    ),
+    ("github_app_api", schemas.GITHUB_APP_API, tools.github_app_api, "🐙"),
+    ("github_app_graphql", schemas.GITHUB_APP_GRAPHQL, tools.github_app_graphql, "📊"),
+    (
+        "github_app_create_issue",
+        schemas.GITHUB_APP_CREATE_ISSUE,
+        tools.github_app_create_issue,
+        "📝",
+    ),
+    (
+        "github_app_comment_issue",
+        schemas.GITHUB_APP_COMMENT_ISSUE,
+        tools.github_app_comment_issue,
+        "💬",
+    ),
+    ("github_app_create_pr", schemas.GITHUB_APP_CREATE_PR, tools.github_app_create_pr, "🔀"),
+    ("github_app_comment_pr", schemas.GITHUB_APP_COMMENT_PR, tools.github_app_comment_pr, "💬"),
+)
+
+
+def register(ctx: object) -> None:
+    """Register Hermes tools, CLI, and bundled skill."""
+    for name, schema, handler, emoji in _TOOLS:
+        ctx.register_tool(  # type: ignore[attr-defined]
+            name=name,
+            toolset=_TOOLSET,
+            schema=schema,
+            handler=handler,
+            emoji=emoji,
+        )
+
+    ctx.register_cli_command(  # type: ignore[attr-defined]
+        name="hermes-github-app",
+        help="Manage the Hermes GitHub App integration",
+        setup_fn=register_cli,
+        handler_fn=cli_main,
+        description="Mint and verify per-agent GitHub App installation tokens.",
+    )
+
+    skill_path = Path(__file__).parent / "skills" / "github-app-workflow"
+    if skill_path.exists():
+        ctx.register_skill("github-app-workflow", skill_path)  # type: ignore[attr-defined]