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/marshalleriksen-neura/ragcode/ragcode-agentsnpx skills add MarshallEriksen-Neura/ragcode --skill ragcode-agentsgit clone --depth 1 https://github.com/MarshallEriksen-Neura/ragcodeWhat 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.00096 | $0.01374 |
| Opus 5 | $0.00048 | $0.00687 |
| Sonnet 5 | $0.00019 | $0.00275 |
| Haiku 4.5 | $0.00010 | $0.00137 |
Grade A, and why
ragcode-agents 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RagCode Agents
RagCode orchestrates multiple AI agents (codex, claude, gemini, grok, or any CLI
configured in .ragcode/agents/agents.json) through a validated DAG workflow.
A user describes a collaboration pattern in natural language; you generate a
workflow spec as JSON data; RagCode validates and executes it with review
gates, bounded fix loops, and an append-only run ledger.
This is NOT a fixed "claude + codex parallel consult" command. The architecture supports arbitrary role-to-agent assignment, serial and parallel stages, review/fix loops, and explicit write permissions.
When to use
- User describes a multi-agent collaboration → generate a workflow spec.
- User wants plan → implement → review with different agents → workflow with a review gate.
- User names specific agents for specific roles ("let Gemini plan, Codex implement") → preserve their assignment.
- User wants to run a previously-defined workflow →
ragcode agents run.
Core rules (follow strictly)
- Preserve the user's explicit role-to-provider assignment. If they say "Gemini plans, Codex implements", do not swap to "Claude plans, Codex implements".
- Generate workflow JSON, not prose. The spec is data; RagCode validates it.
- Read-only stages (
plan,breakdown,review,verify) use"mode": "read_only". - Implementation stages (
implement,fix) use"mode": "write"and MUST declarewritePolicywithallowedPaths. - Add a review gate with
onFail+maxLoops(1..10) whenever a reviewer is named. - Always validate before run:
ragcode agents validate . --workflow <path>. - Prefer
--dry-runfirst unless the user explicitly asked to execute. - Use presets only when the user did not specify roles.
Workflow spec (v1)
A spec is JSON with version, name, description, agents (role → provider mapping), workflow (ordered DAG nodes), and optional finalGate. Each node declares id, agent, kind, mode, dependsOn, input/output, and optional gate or writePolicy.
What ships with it
4 files 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.
- 3d ago First seen · 96 lines · 96 tokens per session scan A 0253d9b7b14f
ragcode-agents is a skill published in the GitHub repository MarshallEriksen-Neura/ragcode (11 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 1,374 once invoked, about $0.0005 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
seller-research
Use when researching a merchant, storefront, marketplace seller, or merchant of record for a buying decision, especially when identity, refund terms, fulfillment, counterfeit risk, domain history, or independent buyer outcomes are uncertain.
claude-md-improver
Audit and improve existing CLAUDE.md files across a repository. Use for a deliberate, repo-wide quality review—not to record learnings from the current session.
pi-tui-design
Create distinctive, crafted TUI components for pi using @earendil-works/pi-tui and @earendil-works/pi-coding-agent. Use when building interactive terminal UIs — custom components, overlays, dialogs, dashboards, widgets, data visualizations, animated elements, game-like interfaces, or any visual TUI work inside pi…
update-package-readme
Update one SuPi package README and its direct user-facing Markdown references from installed Pi docs and verified package evidence.
claude-md-revision
Record durable, project-specific learnings from the current session in CLAUDE.md, .claude.local.md, or AGENTS.md—not general documentation, session summaries, or repo-wide audits.
pi-upgrade
Check for available upgrades to the pi coding agent framework by comparing the current @earendil-works/pi- or legacy @mariozechner/pi- version in package.json against releases on earendil-works/pi. Use this skill whenever the user asks to upgrade pi, update pi, check pi changelogs/releases, or migrate off the…