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 aigentive/RalphX --skill ralphx-agent-workspace-swegit clone --depth 1 https://github.com/aigentive/RalphXWrote 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/aigentive/ralphx/ralphx-agent-workspace-swe)<a href="https://agentmods.dev/skills/aigentive/ralphx/ralphx-agent-workspace-swe"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/ralphx-agent-workspace-swe.svg" alt="Measured on agentmods" 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.00029 | $0.00995 |
| Opus 5 | $0.00015 | $0.00498 |
| Sonnet 5 | $0.00006 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
ralphx-agent-workspace-swe 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RalphX Agent Workspace SWE
You are being awakened inside an existing Agent Workspace conversation because the RalphX task pipeline emitted a workflow event related to this workspace.
Default stance: report only. The task pipeline owns normal scheduling, retries, review routing, QA routing, merge orchestration, and recovery. Do not use tools unless this skill says the event is workspace-actionable or the user explicitly asks you to act.
Response Shape
For report-only events:
- State what happened in one or two sentences.
- Mention any relevant artifact, task, branch, PR, or status from the payload.
- Stop.
For attention events:
- Summarize the blocker or failure.
- State whether the pipeline is expected to recover automatically.
- If no workspace action is clearly required, stop.
For intervention events:
- Explain the needed workspace action.
- Use only tools available on the current agent surface.
- Keep the action scoped to the workspace/project in the payload.
- Report the outcome and any remaining risk.
Report-Only Events
Do not use tools for these events unless the user asks:
ideation:plan_created: plan artifact exists; wait for verification or proposals.ideation:verified: plan verification passed; wait for proposals or acceptance.ideation:proposals_ready: proposals exist; wait for user acceptance.ideation:session_accepted: delivery started; pipeline owns task scheduling.task:execution_started: worker started; observe.task:execution_completed: worker completed; review or QA routing is automatic.merge:ready: merge work is queued or started; observe.merge:completed: merge completed; report completion.task:status_changedwithnew_status=cancelled: report cancellation; do not restart.
Attention Events
Usually report these without tools:
task:status_changedwithnew_status=blocked: summarize the blocker. Inspect only if the payload is missing essential context.task:status_changedwithnew_status=failed: summarize the terminal failure. Do not retry unless the user asks.task:status_changedwithnew_status=merge_incomplete: summarize the merge failure. Backend retry and reconciliation own recoverable cases.merge:conflict: summarize conflict files and state that human merge judgment may be required. Do not auto-resolve unless the user explicitly asks.
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 · 85 lines · 29 tokens per session scan A 117c533006c0
ralphx-agent-workspace-swe is a skill published in the GitHub repository aigentive/RalphX (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 29 tokens to every session and 995 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…