Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ChronoAIProject/NyxID --skill github-via-nyxidgit clone --depth 1 https://github.com/ChronoAIProject/NyxIDWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/chronoaiproject/nyxid/github-via-nyxid)<a href="https://agentmods.dev/skills/chronoaiproject/nyxid/github-via-nyxid"><img src="https://agentmods.dev/badge/skills/chronoaiproject/nyxid/github-via-nyxid/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/chronoaiproject/nyxid/github-via-nyxid"><img src="https://agentmods.dev/badge/skills/chronoaiproject/nyxid/github-via-nyxid.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 63 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00116 | $0.03032 |
| Opus 5.5 | $0.00046 | $0.01213 |
| Sonnet 5.5 | $0.00023 | $0.00606 |
| Haiku 4.5 | $0.00012 | $0.00303 |
Grade A, and why
github-via-nyxid scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operate GitHub via NyxID
Overview
This skill lets an AI agent act on a user's GitHub account using the GitHub REST API — read repos, open issues and pull requests, commit files, trigger Actions, etc. — on the user's behalf.
The one premise: the agent never holds a GitHub token. Every call goes through
NyxID's credential-brokering proxy for the connected service api-github. NyxID
stores the user's GitHub credential (connected via OAuth — "the GitHub account the user
bound in NyxID") encrypted at rest, strips any client Authorization header, injects the
GitHub credential server-side, and forwards the request to https://api.github.com. You
only ever send your NyxID bearer; you never see, request, or log the GitHub token.
What "operate GitHub" really means here: anything the GitHub REST API allows and that the OAuth scopes granted to the
api-githubconnection permit. The ceiling is the granted scopes, not the entire API surface (see Scopes & permissions).
1. Preflight — confirm GitHub is connected
Before the first call, confirm the user has the api-github service connected in NyxID. In an
Aevatar turn, call the available nyxid_service_inventory with {} and select an exact
user_service_id; use only the schema emitted for that request. The CLI and raw HTTP remain
operator alternatives:
- CLI:
nyxid service list --output json→ look for an entry with"slug": "api-github". - Raw HTTP:
GET https://nyx-api.chrono-ai.fun/api/v1/serviceswithAuthorization: Bearer <NYXID_TOKEN>.
If api-github is not present, the user must connect it once (one-click OAuth to their
own GitHub account). Tell them to run:
nyxid service add api-github --oauth
To grant write/admin capabilities up front, request extra scopes at connect time, e.g.:
nyxid service add api-github --oauth --scope "repo,workflow,read:org,gist"
Do not ask the user to paste a GitHub token into chat — the OAuth flow handles it.
(If broader, user-controlled scopes are needed, the api-github-pat service — a
user-supplied Personal Access Token — is the fallback; same proxy, slug api-github-pat.)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 246 lines · 116 tokens per session scan A 5349783a0fd4
github-via-nyxid is a skill published in the GitHub repository ChronoAIProject/NyxID (40 stars, last pushed today), licensed Apache-2.0. It adds 116 tokens to every session and 3,032 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
git-workflow
Follow this team's Git conventions for branching, commit messages, and pull requests.
git-workflow
Git best practices for version control and collaboration.
p4-stream-workflows
P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools. Use when: creating streams, branching, merging, copying between streams, integrating changes, switching workspaces, or managing stream specs in P4.
p4-workspace-setup
P4 workspace setup and management — create, configure, sync, and switch workspaces via P4 MCP tools. Use when: creating workspaces, configuring client specs, syncing files, switching workspaces, or checking workspace status in P4.
issue-management
Create, update, list and search GitHub issues and PRs, list a repository's labels, run milestones, and check for duplicates.