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 diillson/chatcli --skill githubgit clone --depth 1 https://github.com/diillson/chatcliWrote 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/diillson/chatcli/github)<a href="https://agentmods.dev/skills/diillson/chatcli/github"><img src="https://agentmods.dev/badge/skills/diillson/chatcli/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/diillson/chatcli/github"><img src="https://agentmods.dev/badge/skills/diillson/chatcli/github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Data Exfiltration · line 40 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00078 | $0.00670 |
| Opus 5.5 | $0.00031 | $0.00268 |
| Sonnet 5.5 | $0.00016 | $0.00134 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
github scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**`git` + the REST API via `curl`** with a `GITHUB_TOKEN`/`GH_TOKEN` when `gh` is absent. What it actually says
GitHub Workflow
Drive GitHub from the terminal. Prefer the gh CLI (handles auth + API); fall back to
git + the REST API via curl with a GITHUB_TOKEN/GH_TOKEN when gh is absent.
Step 0 — Detect auth method (run once)
- macOS / Linux:
command -v gh >/dev/null && gh auth status >/dev/null 2>&1 && echo gh || echo git - Windows:
if (Get-Command gh -ErrorAction SilentlyContinue) { gh auth status }
If neither gh nor a token is available, tell the user to run gh auth login or set
GITHUB_TOKEN, and stop.
Issues
gh issue list --limit 20
gh issue create --title "Bug: X fails on Y" --body "..."
gh issue view 123 --comments
gh issue close 123
REST fallback: curl -H "Authorization: Bearer $GITHUB_TOKEN" https://api.github.com/repos/OWNER/REPO/issues
Pull request lifecycle
git checkout -b fix/the-thing
# ...edits, then commit (follow repo conventions)...
git push -u origin fix/the-thing
gh pr create --fill # or --title/--body
gh pr checks # watch CI
gh pr view --web # open in browser
gh pr merge --squash --delete-branch # when green + approved
Code review
gh pr diff 456 # read the diff
gh pr view 456 --comments # existing discussion
gh pr review 456 --approve # or --request-changes --body "..."
For a thorough review, read the diff with @read/gh pr diff, check tests/CI, and comment on
concrete lines. Don't approve unseen.
Repo management
gh repo view OWNER/REPO
gh release list
gh workflow list && gh run list --limit 10
Rules
- Respect the repo's branch/commit conventions — read CONTRIBUTING/recent history first.
- Never force-push shared branches or merge without CI green + approval, unless told to.
- Quote the PR/issue number and URL back to the user after acting.
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 · 77 lines · 78 tokens per session scan A e47a5e95d175
github is a skill published in the GitHub repository diillson/chatcli (93 stars, last pushed today), licensed Apache-2.0. It adds 78 tokens to every session and 670 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
gsd-pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
engineer-bot-getting-started
An onboarding guide for an engineering delivery assistant. It helps define a repository, the allowed level of access, and the work needed before reviewing a code change.
05-review
Reviews a change or a diff and says whether it is ready to ship, naming every problem with its fix. Use when the user wants a change checked before it ships. Not for fixing what the review finds, and not for auditing a whole codebase.
01-commit
Create atomic conventional commits; safely retry scoped hook fixes; optionally push. Use when the user wants to commit changes, optionally pushing the branch. Not for amending, rebasing, opening a pull request, or tagging a release.
azure-repos
Expert knowledge for Azure Repos development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when managing Git/TFVC repos, branch policies/PR checks, TFVC→Git migrations, large files, or…
address-pr-feedback
Unified PR feedback workflow - collect, triage, and fix review comments in a single command.