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 iblai/enterprise-agents --skill githubgit clone --depth 1 https://github.com/iblai/enterprise-agentsWrote 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/iblai/enterprise-agents/github)<a href="https://agentmods.dev/skills/iblai/enterprise-agents/github"><img src="https://agentmods.dev/badge/skills/iblai/enterprise-agents/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/iblai/enterprise-agents/github"><img src="https://agentmods.dev/badge/skills/iblai/enterprise-agents/github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00033 | $0.00541 |
| Opus 5.5 | $0.00013 | $0.00216 |
| Sonnet 5.5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub
What it is
GitHub is the leading Git hosting and software collaboration platform, used by enterprise engineering teams for source control, code review, and CI/CD orchestration via GitHub Actions. In this segment the engineering agent uses GitHub in read-only mode to fetch pull request diffs, review comments, commit history, and workflow run results to provide code review assistance, generate release notes, and surface build failures.
When to use this skill
- Reading a pull request diff and review thread to provide feedback or generate a summary
- Fetching the latest GitHub Actions workflow run status for a branch or commit
- Looking up commit history for a repository to understand recent changes
- Retrieving open issues or PR metadata to assess engineering backlog context
- Checking repository topics, language, or contributor stats for onboarding documentation
Credentials
This skill authenticates using variables from ~/.openclaw/.env (template: .env.example at the config root). Required variables:
GITHUB_TOKEN- personal access token or GitHub App installation token withrepoandactions:readscopes
Key operations
GET /repos/{owner}/{repo}/pulls/{pull_number}- fetch a pull request with diff metadataGET /repos/{owner}/{repo}/pulls/{pull_number}/reviews- list review decisions and commentsGET /repos/{owner}/{repo}/commits- list commits on a branchGET /repos/{owner}/{repo}/actions/runs- list workflow runsGET /repos/{owner}/{repo}/issues?state=open- list open issuesGET /search/issues?q=...- cross-repo issue and PR search
Notes
- Use a GitHub App with fine-grained permissions rather than a personal access token in production.
- REST API rate limit is 5,000 requests/hour for authenticated requests; GraphQL counts against the same quota.
- For large diffs, use the
Accept: application/vnd.github.diffheader to get the raw diff. - Treat code content as confidential; do not log or persist source code outside the secure workspace.
- Enterprise GitHub (GHES) uses a different base URL:
https://github.mycompany.com/api/v3.
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 · 37 lines · 33 tokens per session scan A 53986b16c6a4
github is a skill published in the GitHub repository iblai/enterprise-agents (13 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 541 once invoked, about $0.0001 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
babysit
Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.
make-pr-easy-to-review
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".
pr-review-merge
Drive a single pull request to merge-ready across all six criteria (sync, CI, inline comments, conversation, threads, bot re-review of the head commit), then smart-merge it. Source-agnostic library skill invoked by the /tm, /issues, /fix-pr, and /fix-develop commands and by marathon teammates. TRIGGER when a command…
fix-pr
Autonomous PR fixing loop - iterates on CI failures and review comments until green.
pr-describe
Write a pull-request title and body from the current branch's commits and diff against the base branch. Invoke when the user asks to open a PR, draft a PR description, or summarize a branch.
seal
Ships a feature — simplify pass, certify, commit, PR, CI monitoring, review loop, merge. Use when a feature branch is verified and ready to ship.