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 commands/gantisstorm/essentials-claude-code/ralph-configgit clone --depth 1 https://github.com/GantisStorm/essentials-claude-codeWhat 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 | $0.00011 | $0.00536 |
| Opus 5 | $0.00005 | $0.00268 |
| Sonnet 5 | $0.00002 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
ralph-config 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 3d 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
Ralph Config
Write the full recommended RalphTUI configuration for Tasks (json) or Beads workflow.
Arguments
json— Write config for prd.json workflowbeads— Write config for Beads workflow
Instructions
Step 1: Validate Argument
If argument is not json or beads:
Usage: /ralph-config <json|beads>
json - Config for prd.json tasks workflow
beads - Config for Beads workflow
Step 2: Ensure Directory Exists
mkdir -p .ralph-tui
Step 3: Write Config
If argument is json:
cat > .ralph-tui/config.toml << 'EOF'
# RalphTUI config for Tasks (prd.json) workflow
# See: WORKFLOW-TASKS.md#recommended-configurations
configVersion = "2.1"
maxIterations = 0
agent = "claude"
tracker = "json"
autoCommit = false
subagentTracingDetail = "full"
[agentOptions]
model = "claude-opus-4-5-20251101"
[trackerOptions]
[notifications]
sound = "system"
EOF
If argument is beads:
cat > .ralph-tui/config.toml << 'EOF'
# RalphTUI config for Beads workflow
# See: WORKFLOW-BEADS.md#setup-for-beads
configVersion = "2.1"
maxIterations = 0
agent = "claude"
tracker = "beads-bv"
autoCommit = false
subagentTracingDetail = "full"
[agentOptions]
model = "claude-opus-4-5-20251101"
[trackerOptions]
[notifications]
sound = "system"
EOF
Step 4: Report Result
cat .ralph-tui/config.toml
Config written: .ralph-tui/config.toml
Tracker: <json or beads-bv>
Run with:
ralph-tui run --prd <path> # json tracker
ralph-tui run --epic <epic-id> # beads-bv tracker
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.
- 3d ago First seen · 100 lines · 11 tokens per session scan A 20058c907476
ralph-config is a command published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 11 tokens to every session and 536 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-08-30.
Other commands, from other repositories
analyze-repo
Analyze an existing repository's structure, conventions, and guardrails.
go-test
Go TDD workflow with table-driven tests.
retex
Retex - Capture lesson learned dans memory après fix, rollback, erreur.
go-review
Go code review for idiomatic patterns.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
doctor
Run IJFW health check (files, MCP server, hooks, memory, caps, framing).