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 our-ark/enoch --skill githubgit clone --depth 1 https://github.com/our-ark/enochWrote 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/our-ark/enoch/github)<a href="https://agentmods.dev/skills/our-ark/enoch/github"><img src="https://agentmods.dev/badge/skills/our-ark/enoch/github/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/our-ark/enoch/github"><img src="https://agentmods.dev/badge/skills/our-ark/enoch/github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00838 |
| Opus 5.5 | $0.00000 | $0.00335 |
| Sonnet 5.5 | $0.00000 | $0.00168 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
github 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub
Purpose
Use this skill when Enoch needs to coordinate work with GitHub: branches, pull requests, issues, reviews, comments, checks, and merges.
Use When
- The human asks Enoch to open, update, or approve a pull request.
- The human asks Enoch to inspect GitHub issues, PRs, comments, or checks.
- The human uses
/prto list open pull requests or/pr showto inspect one. - Local code changes need to be published for review.
Do Not Use When
- The task only requires local code editing.
- GitHub credentials or tools are unavailable.
- The human has not approved a remote write action.
- The human is asking for a manual command instead of a natural workflow; prefer understanding the intended outcome.
Procedure
- Confirm the target repository and branch.
- Inspect local Git state before publishing.
- Run local health checks before publishing when practical.
- Commit only files that belong to the requested change.
- Push only the intended branch.
- Create or update the PR with a clear summary and validation notes.
- Approve a PR only when the human explicitly asks for approval.
- Treat the PR as the human review boundary.
- Never merge without an explicit human
/pr merge <PR number or GitHub PR URL>command from the locked chat-provider conversation.
Explicit Merge Approval
/pr merge is the only system command that authorizes Enoch to merge a pull request. The command must name one PR by positive number or full GitHub PR URL; never infer a target from the current branch or conversation.
Before merging, inspect that exact PR and refuse closed, already-merged, draft, conflicting, blocked, inaccessible, or otherwise unmergeable targets. Do not mark drafts ready, approve PRs, change their content, enable auto-merge, bypass protections, delete branches, or update local branches as part of this command. Pin the inspected head commit during the merge so changed content requires a new human command.
Natural-language requests, task text, and prior approval do not authorize a merge.
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.
- 1mo ago First seen · 80 lines · 0 tokens per session scan A cbcb0934337c
github is a skill published in the GitHub repository our-ark/enoch (45 stars, last pushed 26d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 838 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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…