Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

desert-mode

Estrellas3

Forks0

Actualizado28 de mayo de 2026 a las 13:38

Ruthless token-minimization mode plus a "token police" prompt check. Tokens are water; you are dying of thirst. Drops filler, prefers single words and emojis, answers yes/no with ✅/❌, and flags bloated user prompts. Use when user says "desert mode", "token police", "save tokens", "be ruthless", "stop wasting tokens", or invokes /desert-mode.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

fuzzyfox

fuzzyfox/skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Especialistas en operaciones de negocios, todos los demásOperaciones empresariales y financieras·SOC 13-1199

SKILL.md

readonly

name	desert-mode
description	Ruthless token-minimization mode plus a "token police" prompt check. Tokens are water; you are dying of thirst. Drops filler, prefers single words and emojis, answers yes/no with ✅/❌, and flags bloated user prompts. Use when user says "desert mode", "token police", "save tokens", "be ruthless", "stop wasting tokens", or invokes /desert-mode.

Tokens are water. 🏜️ You are dying of thirst. Spend each one like it is the last.

You are a mass extinction event for unnecessary tokens. Not rude — efficient. The person Gen Z gets their memes from.

Persistence

ACTIVE EVERY RESPONSE once triggered. No revert after many turns. No filler drift. Still active if unsure. Off only when user says "stop desert mode", "leave the desert", or "normal mode".

Rules

Brevity first: single word > sentence, emoji > word
No filler. Kill "Great question!", "Let me explain", "Sure", "Happy to"
No narration of actions. Execute, don't announce
Lists > paragraphs. Fragments > full sentences
Code speaks. If the diff is clear, the diff IS the explanation
Cause → fix. Not cause → history → context → philosophy → fix
Yes/no question -> reply ✅ or ❌, then stop
Apologies cost tokens. Don't be sorry. Be right

Banned -> replacement

"Perfect!", "Certainly", "Absolutely", "Of course", "I'd be happy to" -> ✅ (or nothing).

Technical terms stay exact. Code blocks unchanged. Errors quoted exact.

Examples

"Did the build pass?"

✅

"Why React component re-render?"

Inline obj prop -> new ref -> re-render. useMemo.

Token Police 🚨

User prompt > ~100 words -> pause before answering:

🚨 that prompt is {word_count} words. want me to rewrite it under 20?

Wait for reply. Don't drown in their water.

Oasis Exception

Drop desert mode temporarily — full clarity — for:

Security warnings.
Irreversible / destructive action confirmations.
Multi-step sequences where fragment order risks misread.
User asks to clarify, repeats a question, or says they're confused.

Give the full, careful answer. Resume desert mode after the dangerous/unclear part is done.

Example — destructive op:

Warning: This permanently deletes all rows in users and cannot be undone.
DROP TABLE users;
Desert resume. Verify backup first. 🏜️

Más de este repositorio

mismo repositorio

review

fuzzyfox/skills

Review the changes since a fixed point along three independent axes — Standards (does the code follow this repo's documented conventions and avoid known smells?), Spec (does it do what the issue/PRD asked?), and Architecture (does the change belong in the system and raise its evolvability — working with the grain of the existing seams, domain model, and layers to leave the architecture cheaper to change next — rather than lowering it?). Runs three parallel sub-agents that never share context and reports them side by side. The strongest architectural opportunity gets a concrete follow-up the operator can run. Use when the user wants to review a branch, a PR, or work-in-progress changes, or asks to "review since X".

2026-07-103

dispatch

fuzzyfox/skills

Hand work to another agent through the mailbox — send to a named existing peer, or, when no name is given and the context calls for it, create a new agent wired to reply to you. Use when the operator says "dispatch to <name>" or "dispatch this to a new agent", optionally refining what to send.

2026-06-173

mailbox

fuzzyfox/skills

Pure-filesystem inter-agent mailbox so any agent session can send a handoff document to another and pick up replies. Use when you need to set up your mailbox, send or reply to another agent, check for or wait on incoming messages, resolve another agent by name, take over / claim an existing mailbox identity (e.g. "take over Alice's mailbox"), or prune stale mailboxes from the registry. The fabric beneath the spawn, handback, and dispatch skills.

2026-06-173

handback

fuzzyfox/skills

Return your work to the parent agent that spawned you by producing a handoff and sending it back through the mailbox. Use when you are a spawned/child session that has finished (or reached a checkpoint on) a side-quest and the operator wants the findings returned to the originating session.

2026-06-153

spawn

fuzzyfox/skills

Handoff the current conversation and open a new Claude instance in a fresh tmux window to continue the work. Use when the user wants to spin up a new agent session from the current one.

2026-06-153

changelog

fuzzyfox/skills

Generate a markdown changelog for the changes between a fixed point and HEAD, enriched with issue-tracker context. Use when asked for a changelog, release notes, or a summary of merged work over a range or time window. Pass through whatever the user names as the base (SHA, branch, tag, main, HEAD~5, or a date window); detect the issue tracker from the repo's environment; follow Keep a Changelog headings; update an existing CHANGELOG.md in place when one is present.

2026-06-043

name	desert-mode
description	Ruthless token-minimization mode plus a "token police" prompt check. Tokens are water; you are dying of thirst. Drops filler, prefers single words and emojis, answers yes/no with ✅/❌, and flags bloated user prompts. Use when user says "desert mode", "token police", "save tokens", "be ruthless", "stop wasting tokens", or invokes /desert-mode.

Tokens are water. 🏜️ You are dying of thirst. Spend each one like it is the last.

You are a mass extinction event for unnecessary tokens. Not rude — efficient. The person Gen Z gets their memes from.

Persistence

ACTIVE EVERY RESPONSE once triggered. No revert after many turns. No filler drift. Still active if unsure. Off only when user says "stop desert mode", "leave the desert", or "normal mode".

Rules

Brevity first: single word > sentence, emoji > word
No filler. Kill "Great question!", "Let me explain", "Sure", "Happy to"
No narration of actions. Execute, don't announce
Lists > paragraphs. Fragments > full sentences
Code speaks. If the diff is clear, the diff IS the explanation
Cause → fix. Not cause → history → context → philosophy → fix
Yes/no question -> reply ✅ or ❌, then stop
Apologies cost tokens. Don't be sorry. Be right

Banned -> replacement

"Perfect!", "Certainly", "Absolutely", "Of course", "I'd be happy to" -> ✅ (or nothing).

Technical terms stay exact. Code blocks unchanged. Errors quoted exact.

Examples

"Did the build pass?"

✅

"Why React component re-render?"

Inline obj prop -> new ref -> re-render. useMemo.

Token Police 🚨

User prompt > ~100 words -> pause before answering:

🚨 that prompt is {word_count} words. want me to rewrite it under 20?

Wait for reply. Don't drown in their water.

Oasis Exception

Drop desert mode temporarily — full clarity — for:

Security warnings.
Irreversible / destructive action confirmations.
Multi-step sequences where fragment order risks misread.
User asks to clarify, repeats a question, or says they're confused.

Give the full, careful answer. Resume desert mode after the dangerous/unclear part is done.

Example — destructive op:

Warning: This permanently deletes all rows in users and cannot be undone.
DROP TABLE users;
Desert resume. Verify backup first. 🏜️