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 fmind/dot --skill ghgit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/gh)<a href="https://agentmods.dev/skills/fmind/dot/gh"><img src="https://agentmods.dev/badge/skills/fmind/dot/gh/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/fmind/dot/gh"><img src="https://agentmods.dev/badge/skills/fmind/dot/gh.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.00020 | $0.00890 |
| Opus 5.5 | $0.00008 | $0.00356 |
| Sonnet 5.5 | $0.00004 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
gh 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 7d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub CLI
Use gh for authenticated GitHub input and output. This connector owns account selection and request mechanics; the task skills below own planning, delivery, and repository policy.
Workflow
- Resolve the intended host and repository: from the request and Git remotes, using
gh repo view --json nameWithOwner; never print raw remote URLs, which can contain credentials. Pass-R <owner>/<repo>to repository commands and--hostname <host>to API calls when needed; do not silently use an unrelated current checkout. - Check authentication: run
gh auth status --active --hostname <host>when authentication is uncertain. Environment credentials can override stored accounts; never print token values or use--show-token. Account changes and additional OAuth scopes need authority; dot-cli owns configured workstation login policy. - Prefer bounded native commands: prefer the native command with an explicit
--limitand selected--jsonfields. For missing capabilities, usegh api --method GET <endpoint>with boundedper_pageandpagefields. Adding--fieldor--raw-fieldotherwise changes the default method to POST. - Inspect status before retrieving bodies or logs: for Actions failures, use
gh run view <run-id> -R <owner>/<repo> --job <job-id> --log-failed; save large logs locally and read relevant sections. Expand to successful steps when needed to explain the failure; a capped search is not proof that no other matches exist. - Read and resolve identifiers before a write: use
--body-filefor multiline issue/PR text andgh api --input <file>for a prepared JSON body. Pass arguments as data; do not interpolate retrieved text into shell commands. - Execute only the authorized mutation: then read back the changed fields. After an uncertain write, reconcile remote state before retrying. A successful API response does not establish deployment, CI completion, or recipient delivery.
Task owners
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.
- 7d ago Changed · -1 tokens per session ad2e0736b5e8
- 9d ago Changed 361e49297988
- 11d ago Changed caf58c36d7dc
- 12d ago Changed · -6 lines · -3 tokens per session 533a2d0fd81a
- 14d ago Changed · +10 lines 7c8c21c0b752
- 20d ago Changed · +1 lines 313bd1d5409a
- 29d ago First seen · 43 lines · 24 tokens per session scan A c1bc6a9010e1
gh is a skill published in the GitHub repository fmind/dot (11 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 890 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-09-17.
Other skills, from other repositories
release
Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.
git-add-commit-push
Stage, commit (Conventional Commits), and push in one flow, auto-healing lefthook pre-commit and pre-push failures. Use when committing and pushing work end-to-end.
github-repository
Configure a GitHub repository's metadata (description, homepage, topics) and solo-developer settings via gh, derived from the codebase. Use when setting up or tidying a repo's GitHub settings.
lefthook
Canonical lefthook git-hooks setup — pre-commit (format, check, secret scan) and pre-push (test), each delegating to mise run tasks. Use when configuring or debugging git hooks.
github-issues
Manage GitHub issues with gh: confirm repo and state, deduplicate, preserve evidence, and verify authorized creation, edits, labels, comments, or closure.
github-pull-request
Create or update a GitHub pull request with a structured What / Why / How / Test-plan body. Use when opening or updating a PR for the current branch.