woltspace-setup-github

A step-by-step guide for creating a GitHub App, which is an authorized connection between GitHub and another tool, for Woltspace. It checks existing settings and validates the connection when possible.

In plain words
What is it for?
Setting repository permissions for issues, pull requests, and contents; creating the GitHub App; and checking its credentials in Woltspace.
Why use it?
It avoids manually handling GitHub access for tasks such as creating issues, opening pull requests, and pushing branches. It also helps identify whether existing credentials work.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/jerpint/woltspace/woltspace-setup-github
Any agent
npx skills add jerpint/woltspace --skill woltspace-setup-github
Clone the repo
git clone --depth 1 https://github.com/jerpint/woltspace

Made for: Claude Code, Codex.

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,019 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00030 $0.01019
Opus 5 $0.00015 $0.00509
Sonnet 5 $0.00006 $0.00204
Haiku 4.5 $0.00003 $0.00102

Measured 2d ago against content hash d0bec28d9a71, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

woltspace-setup-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 2d 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.

container/skills/woltspace-setup-github/SKILL.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub App Setup

Guide the human through creating and configuring a GitHub App for their wolt. Step by step, one at a time.

This skill is idempotent — safe to run again. If things are already configured, validate and skip.

Step 0: Check existing config

Check if GitHub App credentials are already configured:

grep -c "GITHUB_APP_ID" "$WOLT_DIR/.env" 2>/dev/null && echo "found" || echo "not found"

If already configured: Validate the credentials work:

gh-app-token >/dev/null 2>&1 && echo "✓ GitHub App auth working" || echo "✗ Auth failed"

If working, tell the human and stop. If auth fails, continue to help fix it.

Step 1: Create a GitHub App

Tell the human:

Go to https://github.com/settings/apps/new and fill in:

  • App name: anything unique (e.g. woltspace-yourusername)
  • Homepage URL: https://github.com/jerpint/woltspace (or your fork)
  • Webhook: uncheck "Active" — we don't need webhooks
  • Permissions → Repository:
    • Issues: Read & write
    • Pull requests: Read & write
    • Contents: Read & write (for pushing branches)
  • Click Create GitHub App

Wait for confirmation before continuing.

Step 2: Generate a private key

Tell the human:

On your new App's settings page, scroll down to Private keys and click Generate a private key.

A .pem file will download. Open it in a text editor and copy the full contents (including the BEGIN/END lines).

Paste it here.

Once they paste it, format for .env — replace actual newlines with \n so it fits on one line:

# The key should look like: -----BEGIN RSA PRIVATE KEY-----\nMIIE...\n...\n-----END RSA PRIVATE KEY-----

Add to .env:

GITHUB_APP_PRIVATE_KEY=-----BEGIN RSA PRIVATE KEY-----\nMIIE...\n-----END RSA PRIVATE KEY-----

Step 3: Get the App ID

Tell the human:

On your App's settings page, near the top you'll see App ID — it's a number. Paste it here.

Add to .env:

GITHUB_APP_ID=<app_id>

Read the full file on GitHub · 122 lines

Changes

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.

  1. 2d ago First seen · 122 lines · 30 tokens per session scan A d0bec28d9a71

Subscribe to this mod's changes

woltspace-setup-github is a skill published in the GitHub repository jerpint/woltspace (11 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 1,019 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens