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 agentmods add skills/parendumou/nexora/github_readnpx skills add ParendumOU/Nexora --skill github_readgit clone --depth 1 https://github.com/ParendumOU/NexoraWhat 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 | $0.00000 | $0.00508 |
| Opus 5 | $0.00000 | $0.00254 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
github_read 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 2d 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.
What it actually says
GitHub Read
Read access: repos, issues, PRs, files, branches, workflows, runs.
Canonical tool: github_api
ALWAYS use github_api — credentials auto-resolved, raw token never exposed. NEVER call http_request against api.github.com directly.
Common actions
current_user— confirm auth workslist_repos— repos affiliated with token (scope: affiliations/owned/member/all)list_orgs— orgs you belong tolist_org_repos— repos within specific orgrepo_info— single repo metadatalist_issues/list_prs— per-reporead_file— file at reflist_branches/list_commitslist_workflows/list_runs— GitHub Actionssearch— global search
See github_api tool docs for full arg list.
Legacy tools
github_repo_info, github_list_issues, github_list_prs, github_read_file — back-compat only. Prefer github_api.
Requirements
GitHub credential in platform credential store with repo read scope.
Credential = Personal Access Token (PAT) — scoped to human user who issued it:
list_repos scope=affiliations→ ONLY repos PAT owner owns, collaborates on, or is org member of. Random public repos NOT included.list_orgs→ ONLY orgs PAT owner belongs to.- Empty results = PAT genuinely has no affiliation. Do NOT retry guessing org names.
Anti-hallucination
ALWAYS use real API responses verbatim. NEVER invent:
- Repo names, owners, ids, branch names, file paths, URLs, topics.
- "Probable" repos based on context.
- Repos user "should" have — if API didn't return them, not accessible to this PAT.
Inventory smaller than expected → say so plainly, suggest checking PAT scopes (repo, read:org). Never pad list.
Example — inventory
[
{"name": "github_api", "args": {"action": "current_user"}},
{"name": "github_api", "args": {"action": "list_repos", "scope": "owned", "visibility": "private", "max_pages": 5}}
]
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 53 lines · 0 tokens per session scan A bcb80eeb31f6
github_read is a skill published in the GitHub repository ParendumOU/Nexora (19 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 508 tokens. 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
deep-research
深度研究编排方法论：澄清范围、拆解规划、并行调度子智能体调研、对抗式核验、综合成带引用的结构化报告。当任务需要多来源、可追溯、需事实核查的深度研究时使用此技能。.
knowledge-base
使用 Yuxi 知识库进行检索、打开文档、文档内定位和查看思维导图。当用户需要基于已配置知识库回答问题、核验资料或引用文档内容时使用此技能。.
mysql reporter
生成 MySQL 查询报表并生成可视化图表。当用户需要查询 MySQL 数据库并以报表形式展示结果时使用此技能，包括：统计销售数据、分析用户行为、生成业务报表、查询业务指标等。.
background-task
Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
rag-knowledge
Work with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vectorstore }} + {{…