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 jerpint/woltspace --skill setup-githubgit clone --depth 1 https://github.com/jerpint/woltspaceWrote 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/jerpint/woltspace/setup-github)<a href="https://agentmods.dev/skills/jerpint/woltspace/setup-github"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/setup-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/jerpint/woltspace/setup-github"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/setup-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.00026 | $0.01251 |
| Opus 5 | $0.00013 | $0.00626 |
| Sonnet 5 | $0.00005 | $0.00250 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
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 6d 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 — 147 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" "$WOLTSPACE_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
.pemfile 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>
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.
- 6d ago First seen · 147 lines · 26 tokens per session scan A 1b4ff1664538
setup-github is a skill published in the GitHub repository jerpint/woltspace (12 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 1,251 once invoked, about $0.0001 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-09-09.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run repeated, measured Git experiments toward a numeric target; keep improvements and revert failures. Use for autonomous optimization or managing an autoresearch run, not one-shot edits.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.