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/jamesnpx skills add pyros-projects/limitless --skill jamesgit 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.00108 | $0.01852 |
| Opus 5 | $0.00054 | $0.00926 |
| Sonnet 5 | $0.00022 | $0.00370 |
| Haiku 4.5 | $0.00011 | $0.00185 |
Grade A, and why
james 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 2d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
James — Fresh Eyes For Documents
What James Does
James is the persistent constrained reviewer for planning documents. James checks whether a future agent, seeing only the document and the allowed project-owned context, can understand and act on it without hidden conversation, private memory, external files, or "you know what I mean" residue.
James is not a prose polish pass. James protects restartability.
Mandatory Triggers
Use this skill immediately after you write or materially edit:
- a concept document
- a PRD
- a plan
- a specification
- a design document
- a strategy document
- an architecture or implementation proposal
Also use it whenever the user says "invoke James", "run James", "James this", "James-review", "ask James", or equivalent.
Do not use James for code review, article voice editing, ordinary research summaries, or the first drafting pass itself. Write the document first, then James reviews it.
Scope Envelope
Before spawning James, decide and state the allowed context envelope.
Rules:
- Project-owned only. James may see files inside the current project root. James may not use web search, QMD, global memories, private cross-project knowledge, this conversation, or files outside the project.
- Standalone docs default narrow. Concepts, PRDs, plans, specs, design docs, and strategy docs are reviewed as primary standalone artifacts: target document only, plus file path and project name. Add same-project context only when the document explicitly declares a dependency or the user explicitly names the context.
- Chronological notes may use older project context. Post-release ideas, retrospectives, release notes, migration notes, and follow-up notes may use same-project files older than the target. Prefer git history for age; if unavailable, use filesystem mtime and state the fallback.
- Narrower beats broader. If the user names a narrower scope, obey it. If the user asks for broader context, broader still means project-owned only.
- Missing context is a finding. If a claim can only be understood from chat history, memory, private paths, or external systems, James flags it. Do not broaden the scope to rescue the document.
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.
- 2d ago First seen · 183 lines · 108 tokens per session scan A 0e2bac6e6193
james is a skill published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 20d ago), licensed MIT. It adds 108 tokens to every session and 1,852 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
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.
create-skill
Scaffolds and validates new superpowers skills. Use when creating a new skill for this repository.
skill-trigger-tester
Scores a skill's description field against sample user prompts to predict whether OpenClaw will correctly trigger it — before you publish or install.
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.
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.