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 Starfie1d1272/dsh-github-skills --skill githubgit clone --depth 1 https://github.com/Starfie1d1272/dsh-github-skillsWrote 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/starfie1d1272/dsh-github-skills/github)<a href="https://agentmods.dev/skills/starfie1d1272/dsh-github-skills/github"><img src="https://agentmods.dev/badge/skills/starfie1d1272/dsh-github-skills/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/starfie1d1272/dsh-github-skills/github"><img src="https://agentmods.dev/badge/skills/starfie1d1272/dsh-github-skills/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.00000 | $0.00530 |
| Opus 5.5 | $0.00000 | $0.00212 |
| Sonnet 5.5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub
General entrypoint for GitHub triage. Resolve context, classify the request, and route specialist work early. Do not re-implement specialist workflows here.
Capability policy
Use the most specific visible capability whose documented semantics cover
the need. Provider names and tool-name prefixes do not imply capability.
Use local git for local checkout facts; use gh only where no suitable
structured capability covers the operation. Never assume an unavailable
capability exists.
Routing
- general repository / issue / PR triage → stay here
- review feedback →
gh-address-comments - failing GitHub Actions →
gh-fix-ci - push / publish / open a PR — including fork contributions — with any
required branch/commit work →
gh-publish
When a specialist matches, load it with skill() and let it own the
workflow.
Mixed requests may require multiple specialists. Complete review or CI
domain work before publishing; gh-publish does not replace those
workflows.
Triage
- Resolve context. Repo, PR/issue number, or URL given by the user wins; for "this branch" / "the current PR", resolve the local git context first. Ask if still ambiguous.
- Gather the state relevant to the request (issue/PR metadata,
comments, checks) from visible capabilities or
gh. - Classify and handle here, or load the matching specialist and let it own the workflow.
- Report the state and the next action.
Scoped metadata actions (labels, reactions, issue edits) may be applied here only when explicitly requested; everything else routes.
Boundaries
- Flat comments are not review-thread state (see
gh-address-comments). - No CI-log claim without actual logs (see
gh-fix-ci). - Remote writes need explicit user intent or the host approval boundary.
Examples
- "Summarize the open PRs in this repo." → stay here
- "Address the review comments on PR 482." →
gh-address-comments - "Why are the GitHub Actions checks failing on this PR?" →
gh-fix-ci - "Fork awesome-foo, update its README, and open a PR." →
gh-publish
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 · 61 lines · 0 tokens per session scan A 0504fe9f1fbe
github is a skill published in the GitHub repository Starfie1d1272/dsh-github-skills (5 stars, last pushed 10d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 530 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-31.
Other skills, from other repositories
github
Use the connected iPolloWork GitHub service to inspect repositories, pull requests, issues, reviews, and Actions, then route focused work to the review, CI, or publish skill.
github-publish-changes
Publish intentional local changes by confirming scope, creating a branch when needed, staging selected files, committing, pushing, and creating a Draft Pull Request through the connected GitHub service.
github-review-follow-up
Inspect unresolved GitHub pull request review threads, group actionable feedback, implement selected fixes locally, and only reply or resolve threads after explicit user intent.
code-review-zh
A Git-based code review workflow that compares changes from a chosen commit, branch, tag, or merge point. It checks both whether the code follows the repository's written standards and whether it implements the requested specification.
changelog-writing
A writing guide for maintaining a CHANGELOG.md file, which records user-visible changes between software versions. It also covers the release notes taken from the current version section.
ipollowork-maintainable-code
Mandatory iPolloWork code-change gate for modern, minimal, performant, reuse-first implementation and clean repository ownership. Use whenever AI creates, edits, deletes, or refactors application code, server code, packages, scripts, tests, dependencies, schemas, routes, UI, or generated-file workflows. Reuse existing…