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/pyros-projects/limitless/ghost-usernpx skills add pyros-projects/limitless --skill ghost-usergit clone --depth 1 https://github.com/pyros-projects/limitlessWhat 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.00101 | $0.00840 |
| Opus 5 | $0.00051 | $0.00420 |
| Sonnet 5 | $0.00020 | $0.00168 |
| Haiku 4.5 | $0.00010 | $0.00084 |
Grade A, and why
ghost-user 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 yesterday.
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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ghost User
Overview
This skill simulates first contact.
Not a power user. Not a chaos monkey. Not a formal usability study.
Just a quiet first-time user moving through the surface with no internal context and no special sympathy for what the builders meant.
When to Use
Use this when:
- a flow feels "obvious" and you want to verify that
- onboarding is thin or absent
- the product may be assuming too much prior knowledge
- you want a first-contact honesty pass without setting up full user research
Do not use this to invent edge cases for sport. Stay close to plausible first-use reality.
If you have already read project docs, architecture notes, or implementation details in the current session, explicitly say that your ghost-user pass is partially contaminated and flag which observations may be insider-influenced.
What to Produce
Walk through the product or flow as the ghost user would:
- what they notice first
- what they assume
- what confuses them
- what feels invisible
- what requires author knowledge to decode
Narrate it plainly. The power of this skill is not sophistication. It is honesty.
Working Loop
-
Forget the author view. Start from the surface alone. Do not read README files, docs, architecture notes, or source code before the pass if the raw product surface is available.
-
Walk the first contact honestly. What do I see? What do I think this means? What do I try next?
-
Notice the invisible assumptions. Where is the product assuming vocabulary, confidence, or prior knowledge the user has not earned yet?
-
End with the highest-leverage fixes. Do not drown the user in notes. Point to the few changes that would most improve first contact.
Suggested Output Shape
What I notice firstWhat I assumeWhere I get confusedWhat required inside knowledgeThe 3 highest-leverage fixes
Tiny Example
What I notice first: I see a button calledInit.What I assume: Maybe it creates something, but I do not know what.Where I get confused: Clicking it changes the page, but nothing tells me what happened.What required inside knowledge: Knowing thatInitmeans "create a new workspace."The 3 highest-leverage fixes: Rename the button, add immediate confirmation, and show the created thing in context.
What ships with it
1 file 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.
- yesterday First seen · 105 lines · 101 tokens per session scan A 0fe5a1d69de1
ghost-user is a skill published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 19d ago), licensed MIT. It adds 101 tokens to every session and 840 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-31.
Other skills, from other repositories
community-skill-radar
Searches Reddit communities for OpenClaw pain points and feature requests, scores them by signal strength, and writes a prioritized PROPOSALS.md for you to review and act on.
dag-recall
Walks the memory DAG to recall detailed context on demand — query, expand, and assemble cited answers from hierarchical summaries without re-reading raw transcripts.
expansion-grant-guard
YAML-based delegation grant ledger — issues, validates, and tracks scoped permission grants for sub-agent expansions with token budgets and auto-expiry.
memory-dag-compactor
Builds hierarchical summary DAGs from MEMORY.md with depth-aware prompts — leaf summaries preserve detail, higher depths condense to durable arcs, preventing information loss during compaction.
memory-graph-builder
Parses OpenClaw's flat MEMORY.md into a structured knowledge graph — detects duplicates, contradictions, and stale entries, then builds a compressed memory digest optimized for system prompt injection.
create-skill
Scaffolds and validates new superpowers skills. Use when creating a new skill for this repository.