github-self-hosted-runner SKILL.md skillB

github-self-hosted-runner from markphelps/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add markphelps/skills/github-self-hosted-runner@git:20261004.11832f3

Pins git:20261004.11832f3 in mdr.lock. Pin the fingerprint instead.

Audit grade
B, 16 of 17 checks passed
Kind
SKILL.md skill
Repository
markphelps/skills
Path
development/skills/github-self-hosted-runner/SKILL.md
Versions recorded
2
Latest version
git:20261004.11832f3, committed Oct 4, 2026
First version recorded
Sep 6, 2026
Size
11,887 bytes
Repository stars
6
License
MIT

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# GitHub self-hosted runner

Create one isolated runner instance per repository or organization registration.
Detect the operating system first and use the matching service manager: systemd
on Linux or launchd on macOS. Determine the account that should own and run the
runner instead of assuming a fixed username or home directory.

On Linux, resolve the account and paths with:

```bash
RUNNER_USER="${RUNNER_USER:-${SUDO_USER:-$USER}}"
RUNNER_GROUP="$(id -gn "$RUNNER_USER")"
RUNNER_HOME="$(getent passwd "$RUNNER_USER" | cut -d: -f6)"
RUNNER_ROOT="$RUNNER_HOME/actions-runners"
```

On macOS, resolve the account without relying on `getent`:

```bash
RUNNER_USER="${RUNNER_USER:-${SUDO_USER:-$USER}}"
RUNNER_GROUP="$(id -gn "$RUNNER_USER")"
RUNNER_HOME="$(dscl . -read "/Users/$RUNNER_USER" NFSHomeDirectory | awk '{print $2}')"
RUNNER_ROOT="$RUNNER_HOME/actions-runners"
```

Validate that the values are non-empty and `RUNNER_HOME` exists. When commands
run through `sudo`, do not accidentally use root's `$USER` or `$HOME` as the
runner account.

Namespace every instance by target slug:

- Directory: `$RUNNER_ROOT/<slug>`
- Runner name: `<hostname>-<slug>`
- Custom label: `<slug>`
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ggqasga4phmpdj2u/b1ce2493195600c90ea59c442cc7595b00e06ec9408cb8846be327266fa01b29.json

Then /plugin install github-self-hosted-runner@markdownregistry-ggqasga4phmpdj2u in Claude Code. It installs git:20261004.11832f3, the one graded B here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add markphelps/skills/github-self-hosted-runner@sha256:b1ce2493195600c9

The line at the top of this page pins the label git:20261004.11832f3, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_ggqasga4phmpdj2u.svg)](https://markdownregistry.com/a/art_ggqasga4phmpdj2u)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in markphelps/skills/github-self-hosted-runner since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of github-self-hosted-runner from somewhere else? Ask it: where did my github-self-hosted-runner come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 2 versions of this file, between Sep 6, 2026 and Oct 4, 2026, about one every 28 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261004.11832f3 latest2026-10-04 11832f3 11,887 BB view · diff
git:20260906.23d8e792026-09-06 23d8e79 7,850 BB view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

B  16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • fail: Frontmatter declares a description
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Size between 200 bytes and 200 KB (11887 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

markphelps/skills · 6 stars · license MIT · pushed 2026-11-15 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ggqasga4phmpdj2u
GET https://markdownregistry.com/api/v1/resolve?ref=markphelps/skills/github-self-hosted-runner
GET https://markdownregistry.com/api/v1/blob/b1ce2493195600c90ea59c442cc7595b00e06ec9408cb8846be327266fa01b29

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from markphelps/skills

AGENTS.md AGENTS.md file
markphelps/skills · AGENTS.md
git:20260928.fb986fd · audit A · 6 stars
AGENTS.md@development AGENTS.md file
markphelps/skills · development/AGENTS.md
git:20261115.1fb19c9 · audit A · 6 stars
cli-design SKILL.md skill
markphelps/skills · development/skills/cli-design/SKILL.md · Design, build, or review command-line interfaces using the Command Line Interface Guidelines from clig.dev. Use this…
git:20260625.24602d6 · audit A · 6 stars
codebase-landing-copy SKILL.md skill
markphelps/skills · development/skills/codebase-landing-copy/SKILL.md
git:20260919.81b4b4e · audit B · 6 stars
context-file-tuneup SKILL.md skill
markphelps/skills · development/skills/context-file-tuneup/SKILL.md
git:20260523.c579973 · audit B · 6 stars
council SKILL.md skill
markphelps/skills · development/skills/council/SKILL.md
git:20261115.1fb19c9 · audit B · 6 stars
course-notes SKILL.md skill
markphelps/skills · development/skills/course-notes/SKILL.md
git:20261014.72d6c82 · audit C · 6 stars
decision-records SKILL.md skill
markphelps/skills · development/skills/decision-records/SKILL.md
git:20260913.a6ef6f5 · audit B · 6 stars
feature-map SKILL.md skill
markphelps/skills · development/skills/feature-map/SKILL.md
git:20260924.fb60020 · audit B · 6 stars
github-pr-fixup SKILL.md skill
markphelps/skills · development/skills/github-pr-fixup/SKILL.md
git:20260528.5314212 · audit B · 6 stars
oss-marketing SKILL.md skill
markphelps/skills · development/skills/oss-marketing/SKILL.md
git:20260702.608072d · audit B · 6 stars
oss-repo-readiness SKILL.md skill
markphelps/skills · development/skills/oss-repo-readiness/SKILL.md
git:20260702.608072d · audit B · 6 stars

Every file in markphelps/skills

Browse by kind, by grade B, or by owner.