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 agentmods add skills/posthog/posthog-foss/depot-github-runnersnpx skills add PostHog/posthog-foss --skill depot-github-runnersgit clone --depth 1 https://github.com/PostHog/posthog-fossWrote 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/posthog/posthog-foss/depot-github-runners)<a href="https://agentmods.dev/skills/posthog/posthog-foss/depot-github-runners"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/depot-github-runners.svg" alt="Measured on agentmods" 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.00152 | $0.02733 |
| Opus 5 | $0.00076 | $0.01367 |
| Sonnet 5 | $0.00030 | $0.00547 |
| Haiku 4.5 | $0.00015 | $0.00273 |
Grade A, and why
depot-github-runners 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 today.
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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Depot GitHub Actions Runners
Depot provides managed, ephemeral, single-tenant GitHub Actions runners. Drop-in replacement for GitHub-hosted runners — change the runs-on label and everything else stays the same.
Requirement: Repository must be owned by a GitHub organization (not a personal account).
Depot runners are not Depot CI
Depot runners keep GitHub Actions as the engine, so the workflow lives in .github/workflows/ and the checks still come from the github-actions app.
Depot CI is a different product: it reads .depot/workflows/, which GitHub Actions ignores, and posts its own check runs from the depot-code-access app.
Use the depot-ci skill for that one.
Its references/posthog-check-run-semantics.md compares what each engine reports for a skipped, empty-matrix or continue-on-error job, and how GitHub and the Trunk merge queue score those conclusions.
Setup
- Depot dashboard → GitHub Actions → Connect to GitHub → Install Depot GitHub App
- For public repos: GitHub org settings → Actions → Runner groups → Default → "Allow public repositories"
- Update
runs-onin your workflow files
Org Context Check for Multi-Org Users
If a user belongs to multiple organizations and expected repos/settings/runners are not visible, verify Depot org context first:
depot org show # Current org ID
depot org list # Orgs the user belongs to
depot org switch <org-id> # Optional: set default org
For commands that support it, pass --org <org-id> to target the org where the workflow/repo lives.
Runner Labels
Use a single label. Format: depot-{os}-{version}[-{arch}][-{size}]
Ubuntu (x86, AMD)
| Label | CPUs | RAM | Disk | $/min | Minutes multiplier |
|---|---|---|---|---|---|
depot-ubuntu-24.04 |
2 | 8 GB | 100 GB | $0.004 | 1x |
depot-ubuntu-24.04-4 |
4 | 16 GB | 130 GB | $0.008 | 2x |
depot-ubuntu-24.04-8 |
8 | 32 GB | 150 GB | $0.016 | 4x |
depot-ubuntu-24.04-16 |
16 | 64 GB | 180 GB | $0.032 | 8x |
depot-ubuntu-24.04-32 |
32 | 128 GB | 200 GB | $0.064 | 16x |
depot-ubuntu-24.04-64 |
64 | 256 GB | 250 GB | $0.128 | 32x |
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.
- today Changed · +17 lines · +24 tokens per session fb028f5ba9a6
- 6d ago First seen · 214 lines · 128 tokens per session scan A 141923e6f83f
depot-github-runners is a skill published in the GitHub repository PostHog/posthog-foss (712 stars, last pushed today), licensed MIT. It adds 152 tokens to every session and 2,733 once invoked, about $0.0008 per session on Opus 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.