Borrowing it
Nothing to install: this file belongs to Undertone0809/rudder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Undertone0809/rudder/main/.agents/skills/maintainer/rudder-desktop-dev-recovery-maintainer/SKILL.mdgit clone --depth 1 https://github.com/Undertone0809/rudderWrote 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/undertone0809/rudder/rudder-desktop-dev-recovery-maintainer)<a href="https://agentmods.dev/skills/undertone0809/rudder/rudder-desktop-dev-recovery-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/rudder-desktop-dev-recovery-maintainer/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/undertone0809/rudder/rudder-desktop-dev-recovery-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/rudder-desktop-dev-recovery-maintainer.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.00118 | $0.01707 |
| Opus 5 | $0.00059 | $0.00853 |
| Sonnet 5 | $0.00024 | $0.00341 |
| Haiku 4.5 | $0.00012 | $0.00171 |
Grade A, and why
rudder-desktop-dev-recovery-maintainer 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rudder Desktop Dev Recovery Maintainer
Recover the exact Desktop path the user named. API health alone is not Desktop health, and a healthy server belonging to another checkout is not evidence.
Exclusive Outcome
RECOVERED: the named Desktop path opened and its runtime identity plus requested behavior were observed.BLOCKED: the failing layer and remaining external decision or dependency are proven.
Do not claim recovery from code inspection, typecheck, a dry run, or an unrelated healthy server.
Classify The Target Before Resolving Runtime Identity
Development or worktree target
- Inspect the current checkout's
.rudder/config.jsonand safe keys from.rudder/.env. - Follow
scripts/dev-local-env.mjsto resolve the effective Rudder home, instance, port, and descriptor. - Read that instance's
runtime/server.json; use itsapiUrl. - Only fall back to shared
3100/devafter proving the checkout has no isolation configuration.
Typical current commands:
pnpm dev
pnpm dev:watch
pnpm --filter @rudderhq/desktop dev
pnpm --filter @rudderhq/desktop smoke
Packaged or prod-local target
Do not infer packaged identity from the current checkout's dev configuration. Use installed-app boot evidence and the prod-local runtime. Unless an explicit override or boot record proves otherwise, expect:
RUDDER_LOCAL_ENV=prod_local- instance
default - descriptor
~/.rudder/instances/default/runtime/server.json
For package-sensitive changes, the required proof path is:
pnpm desktop:verify
In either mode, verify that health matches the expected instanceId,
localEnv, and runtimeOwnerKind before inspecting product data.
Migration-History Recovery Route
Use this route whenever startup, update, or recovery mentions pending
migrations, the migration journal, schema history, a backup, rollback, or a
candidate built from another history. Before inspecting or changing a
non-empty instance, read references/migration-history-recovery.md. It defines
the manifest/live-journal comparison, forward-known/unknown/
checksum-mismatch/fork classifications, verified backup and free-space
gates, isolated forward validation, installed-app and same-workspace proof, and
the boundary between RECOVERED and candidate-only or backup-only evidence.
What ships with it
3 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.
- 6d ago Changed · +2 lines e40239595784
- 12d ago First seen · 182 lines · 118 tokens per session scan A eb1202ec5922
rudder-desktop-dev-recovery-maintainer is a skill published in the GitHub repository Undertone0809/rudder (289 stars, last pushed today), licensed Apache-2.0. It adds 118 tokens to every session and 1,707 once invoked, about $0.0006 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.