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 aiya000/dotfiles --skill vrchat-force-purge-all-favorite-worldsgit clone --depth 1 https://github.com/aiya000/dotfilesWrote 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/aiya000/dotfiles/vrchat-force-purge-all-favorite-worlds)<a href="https://agentmods.dev/skills/aiya000/dotfiles/vrchat-force-purge-all-favorite-worlds"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/vrchat-force-purge-all-favorite-worlds/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/aiya000/dotfiles/vrchat-force-purge-all-favorite-worlds"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/vrchat-force-purge-all-favorite-worlds.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 41 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 90 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00051 | $0.02683 |
| Opus 5 | $0.00026 | $0.01341 |
| Sonnet 5 | $0.00010 | $0.00537 |
| Haiku 4.5 | $0.00005 | $0.00268 |
Grade A, and why
vrchat-force-purge-all-favorite-worlds scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(curl:*), Bash(jq:*), Bash(mkdir:*), Bash(kill:*), Bash(ps:*), Bash(touch:*), Bash(rm-dust:*), Bash(sleep:*) How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vrchat-force-purge-all-favorite-worlds
Deletes ALL favorited worlds (all groups: worlds1..worldsN) from the authenticated
VRChat account. This is destructive and irreversible via the API — favorites are not
recoverable after deletion.
Fixed paths used by this skill (intentionally NOT the per-session scratchpad — see Notes):
WORKDIR=/tmp/vrchat-force-purge-all-favorite-worldsCOOKIE_JAR=$WORKDIR/cookies.jarFAVORITES_JSON=$WORKDIR/favorites.jsonLOG=$WORKDIR/delete.logLOCKFILE=/tmp/vrchat-force-purge-all-favorite-worlds.lock(sibling ofWORKDIR, not inside it)
Behavior
-
Credential precondition check — before anything else:
- Verify both
$VRC_USERand$VRC_PASSare set and non-empty - If either is missing: stop immediately. Tell the user to run
export VRC_USER=... VRC_PASS=...(optionallyVRC_CONTACT=..., see Notes) in their shell, then re-invoke this skill. Do not attempt login with a partial/empty credential
- Verify both
-
Concurrency guard (lock):
mkdir -p "$WORKDIR"- If
$LOCKFILEexists: read the PID from it, check liveness withkill -0 <PID>- Alive → stop, report another purge is already running (show PID + lock timestamp), refuse
- Dead (stale) → note it,
rm-dust -f "$LOCKFILE", continue
- Do not write the lock yet — it's written atomically with the delete loop in step 8
-
Authenticate:
rm-dust -f "$COOKIE_JAR"first (no stale cookies)UA="vrchat-force-purge-all-favorite-worlds/1.0 (${VRC_CONTACT:-contact-not-provided})"- Call
api.vrchat.clouddirectly (neverapi.vrchat.com— it 307-redirects cross-host and curl drops theAuthorizationheader on that redirect):curl -sS -u "$VRC_USER:$VRC_PASS" -A "$UA" -c "$COOKIE_JAR" -b "$COOKIE_JAR" -o "$WORKDIR/auth.json" -w '%{http_code}' https://api.vrchat.cloud/api/1/auth/user - Non-2xx → stop, report likely-bad credentials, no blind retry
- If
auth.jsoncontainsrequiresTwoFactorAuth→ step 3, else → step 4
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.
- 12d ago First seen · 164 lines · 51 tokens per session scan A 3d4c89c06402
vrchat-force-purge-all-favorite-worlds is a skill published in the GitHub repository aiya000/dotfiles (19 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 2,683 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
restart__pull_request
A pull-request restart workflow for replacing a messy review with a new pull request containing one clean commit and a summary of the earlier discussion.
rescue__pull_request_review
An automated workflow for handling GitHub pull-request review comments, applying requested code changes, committing them, and pushing them back.
submit__pull_request
An automated pull-request submission workflow. A pull request is a request for a code change to be reviewed and merged; this workflow writes its explanation, creates it, watches its automated checks, and fixes failed checks.
write__pull_request
A workflow for writing a pull request description, the explanation attached to a proposed code change for review. It analyses the changes and commit history.
monitor__ci_status
An automated monitor for GitHub Actions, the service that runs checks such as tests after code changes. It watches all checks after a pull request or a push to a pull-request branch and can invoke a failure-recovery process.
monitor__pull_request_conflict
An automated check for GitHub pull requests, which are proposed code changes awaiting review or merging.