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 rubenmarcus/ralph-starter --skill ralph-githubgit clone --depth 1 https://github.com/rubenmarcus/ralph-starterWrote 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/rubenmarcus/ralph-starter/ralph-github)<a href="https://agentmods.dev/skills/rubenmarcus/ralph-starter/ralph-github"><img src="https://agentmods.dev/badge/skills/rubenmarcus/ralph-starter/ralph-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/rubenmarcus/ralph-starter/ralph-github"><img src="https://agentmods.dev/badge/skills/rubenmarcus/ralph-starter/ralph-github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00015 | $0.00215 |
| Opus 5.5 | $0.00006 | $0.00086 |
| Sonnet 5.5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
ralph-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 1mo 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.
What it actually says
Fetch specs from GitHub issues or PRs and run an autonomous coding loop to implement them.
-
Use
ralph_fetch_specwithsource: "github"to preview the issue/PR:identifier: repo URL,"owner/repo#123", or issue URL- Use
projectto filter by repo,labelto filter by label
-
Use
ralph_runto build from the spec:- Set
from: "github"and provideproject(owner/repo) - Optionally filter with
label(e.g., "good first issue", "bug") - Set
auto: true,commit: true,validate: truefor full automation
- Set
-
For batch processing multiple issues, use
ralph_runwithauto: true— each issue gets its own branch and PR.
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.
- 1mo ago First seen · 18 lines · 15 tokens per session scan A 463cd214e41e
ralph-github is a skill published in the GitHub repository rubenmarcus/ralph-starter (107 stars, last pushed 8d ago), licensed MIT. It adds 15 tokens to every session and 215 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-08-30.
Other skills, from other repositories
create-pr
Create GitHub pull requests with Conventional Commits-formatted titles and structured PR bodies. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
pr-writer
ALWAYS use this skill when creating or updating pull requests — never create or edit a PR directly without it. Follows Sentry conventions for PR titles, descriptions, and issue references. Trigger on any create PR, open PR, submit PR, make PR,...
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
github-multi-repo
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
resolve-pr-comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".