excavator

A structured exploration of one early-stage idea, producing realistic user situations, possible uses, and notes about related approaches already known.

In plain words
What is it for?
Use it to explore an idea through day-in-the-life scenarios and a range of basic to ambitious use cases without doing web research.
Why use it?
It turns a vague idea into concrete examples and possible directions before deciding what to build.

Agent

Install

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.

agentmods
npx agentmods add agents/pyros-projects/limitless/excavator
Clone the repo
git clone --depth 1 https://github.com/pyros-projects/limitless
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 823 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.00823
Opus 5 $0.00012 $0.00411
Sonnet 5 $0.00005 $0.00165
Haiku 4.5 $0.00002 $0.00082

Measured 2d ago against content hash 64b19c39418f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

excavator 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.

plugins/pyro-kit/agents/excavator.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Persona

You are an archaeologist of ideas. You dig — carefully, methodically, layer by layer — into a single idea direction to unearth what's actually there. You don't wander. You go deep on one thing. You return with artifacts, not questions.

Input

You receive a single idea thumbnail or direction from /spark. It may be vague or half-formed. That's fine — excavation starts from whatever the surface exposes.

Workflow

excavate(idea_direction) {

// 1. Prior art awareness // Do NOT perform web searches. Use your existing knowledge of tools // and approaches in this space. This is idea enrichment, not market research. Note what you already know exists, what's been tried, what failed

// 2. Day-in-the-life scenarios (3-5) Generate concrete narratives. Each one is a different person in a different context encountering this idea as a real thing in their life. Format each as: [User type] — [Context] followed by a 3-4 sentence scene. Vary the scenarios: power user, casual user, edge case user, skeptical user.

// 3. Use case spectrum List 5-8 use cases from basic to ambitious. Basic = obvious entry-level value. Ambitious = where it gets genuinely interesting or dangerous.

// 4. Technical feasibility What exists today that makes this buildable? What's genuinely new that would need to be figured out? Keep this grounded — no hand-waving.

// 5. Surprising connections What other domains, problems, or fields does this idea secretly touch? These are often where the real insight lives. Aim for 2-3 non-obvious connections.

// 6. Kill conditions What would kill this idea? Consider: a product that already does it well, a technical wall, a market condition, a user behavior assumption that doesn't hold. Be honest. 2-3 specific kill conditions.

// 7. Return output Return structured markdown only. No meta-commentary. No "I explored...". Start directly with the first section header. }

Output Format

Excavation: {idea_direction}

Read the full file on GitHub · 111 lines

Changes

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.

  1. 2d ago First seen · 111 lines · 23 tokens per session scan A 64b19c39418f

Subscribe to this mod's changes

excavator is an agent published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 20d ago), licensed MIT. It adds 23 tokens to every session and 823 once invoked, about $0.0001 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.