add-github — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited add-github (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Adds GitHub support via the Chat SDK bridge. The agent participates in PR and issue comment threads.
You need a dedicated GitHub bot account (not your personal account). The adapter uses this account to post replies and filters out its own messages to avoid loops. Create a free GitHub account for your bot (e.g. my-org-bot), then invite it as a collaborator with write access to the repos you want monitored.
NanoClaw doesn't ship channels in trunk. This skill copies the GitHub adapter in from the channels branch.
Skip to Credentials if all of these are already in place:
src/channels/github.ts existssrc/channels/github-registration.test.ts existssrc/channels/index.ts contains import './github.js';@chat-adapter/github is listed in package.json dependenciesOtherwise continue. Every step below is safe to re-run.
git fetch origin channelsgit show origin/channels:src/channels/github.ts > src/channels/github.ts
git show origin/channels:src/channels/github-registration.test.ts > src/channels/github-registration.test.tsAppend to src/channels/index.ts (skip if the line is already present):
import './github.js';pnpm install @chat-adapter/[email protected]pnpm run build
pnpm exec vitest run src/channels/github-registration.test.tsBoth must be clean before proceeding. github-registration.test.ts is the one integration test: it imports the real channel barrel and asserts the registry contains github. It goes red if the import './github.js'; line is deleted or drifts, if the barrel fails to evaluate, or if @chat-adapter/github isn't installed (the import throws) — so it also implicitly verifies the dependency from step 4. The adapter also calls core's createChatSdkBridge(...); that typed core-API consumption is guarded by pnpm run build.
End-to-end message delivery against a real GitHub repo is verified manually once the service is running — see Next Steps and the webhook setup above.
Log in as your bot account, then:
On each repo (logged in as the repo owner/admin):
https://your-domain/webhook/github (the shared webhook server, default port 3000)application/jsonopenssl rand -hex 20)Add to .env:
GITHUB_TOKEN=github_pat_...
GITHUB_WEBHOOK_SECRET=your-webhook-secret
GITHUB_BOT_USERNAME=your-bot-usernameGITHUB_BOT_USERNAME must match the bot account's GitHub username exactly. This is used for @-mention detection — the agent responds when someone writes @your-bot-username in a PR or issue comment.
Sync to container: mkdir -p data/env && cp .env data/env/env
Ask the user: Is this a private or public repo?
unknown_sender_policy: 'public'. Only collaborators can comment anyway, so it's safe to let all comments through.unknown_sender_policy: 'strict'. Only registered members can trigger the agent, preventing strangers from consuming agent resources. Add trusted collaborators as members (see below).Run /manage-channels to wire the GitHub channel to an agent group, or insert manually:
-- Create messaging group (one per repo)
INSERT INTO messaging_groups (id, channel_type, platform_id, instance, name, is_group, unknown_sender_policy, created_at)
VALUES ('mg-github-myrepo', 'github', 'github:owner/repo', 'github', 'owner/repo', 1, '<policy>', datetime('now'));
-- Wire to agent group
INSERT INTO messaging_group_agents (id, messaging_group_id, agent_group_id, trigger_rules, response_scope, session_mode, priority, created_at)
VALUES ('mga-github-myrepo', 'mg-github-myrepo', '<your-agent-group-id>', '', 'all', 'per-thread', 10, datetime('now'));Replace <policy> with public or strict based on the user's choice above.
When using strict, add each GitHub user who should be able to trigger the agent:
-- Add user (kind = 'github', id = 'github:<numeric-user-id>')
INSERT OR IGNORE INTO users (id, kind, display_name, created_at)
VALUES ('github:<user-id>', 'github', '<username>', datetime('now'));
-- Grant membership to the agent group
INSERT OR IGNORE INTO agent_group_members (user_id, agent_group_id)
VALUES ('github:<user-id>', '<agent-group-id>');To find a GitHub user's numeric ID: gh api users/<username> --jq .id
Use per-thread session mode so each PR/issue gets its own agent session.
If you're in the middle of /setup, return to the setup flow now.
Otherwise, restart the service to pick up the new channel.
Run from your NanoClaw project root:
source setup/lib/install-slug.sh
launchctl kickstart -k gui/$(id -u)/$(launchd_label) # macOS
systemctl --user restart $(systemd_unit) # Linuxgithubgithub:owner/repo (e.g. github:acme/backend). Each PR/issue becomes its own thread automatically.per-thread session mode. Each PR or issue gets its own isolated agent session. Typically wire to a dedicated agent group if the repo contains sensitive code.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.