egregore: Skill for Claude Code

.claude/skills/summon/SKILL.md

summon is a skill for Claude Code from egregore-labs/egregore. It costs 35 tokens per session (2,728 once invoked), scanned A, original, MIT.

A guided setup for a long-running software agent that runs on a schedule or waits for specified conditions. It asks questions, creates a plan you can review, and then starts the agent.

In plain words
What is it for?
Use it to set up scheduled jobs, condition-based monitoring, or an agent that keeps watching and acting over time.
Why use it?
It helps turn a vague request for recurring or monitoring work into a clear process before anything starts.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the AskUserQuestion tool.

This is egregore-labs/egregore's own configuration. It tells Claude Code how to work on egregore itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything egregore configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is CONTEXT=$(bash bin/graph-batch.sh '[.

Reuse

Borrowing it

Nothing to install: this file belongs to egregore-labs/egregore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/summon/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/egregore-labs/egregore

Made for: Claude Code.

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

agentmods badge for summon

README.md
[![agentmods](https://agentmods.dev/badge/skills/egregore-labs/egregore/summon/github.svg)](https://agentmods.dev/skills/egregore-labs/egregore/summon)
Your own site
<a href="https://agentmods.dev/skills/egregore-labs/egregore/summon"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/summon/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.

agentmods 80×15 button for summon

Your own site · 80×15
<a href="https://agentmods.dev/skills/egregore-labs/egregore/summon"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/summon.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,728 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00035 $0.02728
Opus 5 $0.00017 $0.01364
Sonnet 5 $0.00007 $0.00546
Haiku 4.5 $0.00003 $0.00273

Measured 9d ago against content hash a70d74cac099, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

summon 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 9d 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.

.claude/skills/summon/SKILL.md · 241 lines

How it starts

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

/summon — Design and Launch a Persistent Agent Process

Summon a spirit — a persistent agent that runs on a schedule or watches for conditions. Unlike /loop (dumb scheduler), /summon designs the process through adaptive questioning, produces a reviewable spec, then launches it.

When to invoke

Trigger phrases: "summon", "create a loop", "set up a recurring", "watch for", "monitor", "keep an eye on", "babysit", "run something every", "I want an agent that"

Not this command:

  • Quick one-shot schedule → /loop directly (user already knows what they want)
  • One-time task → just do it, no spirit needed

Mode detection

MODE=$(jq -r '.mode // "connected"' egregore.json 2>/dev/null)

Local mode (mode === "local"): Skip ALL bin/graph.sh, bin/graph-batch.sh, and bin/notify.sh calls — do NOT run them. Do NOT show any graph-related messaging.

Local-mode adjustments:

  • Phase 1: Skip the graph scan. Generate options from conversation context, memory/quests/ files, and .spirits/ directory instead of the graph.
  • Phase 5: Skip Spirit node creation in Neo4j. Write the spec file to .spirits/{name}.json and create the CronCreate schedule — these work without the graph.
  • Phase 6: Skip LoopReport creation in Neo4j. The TUI report still renders, but the graph artifact is not created.
  • Managing Spirits: Read from .spirits/ directory instead of querying the graph. Suspend/resume only uses CronDelete/CronCreate, not graph updates.

Instructions

Phase 1: Intent Discovery

Start with one open question via AskUserQuestion:

What should this spirit do?

Connected mode: Options should be derived from current graph context — not hardcoded. Before asking, run a lightweight graph scan to understand what's happening:

# Get active quests, recent sessions, health signals
CONTEXT=$(bash bin/graph-batch.sh '[
  {"statement": "MATCH (q:Quest) WHERE q.status IN [\"active\", \"in-progress\"] RETURN q.id, q.title LIMIT 10", "parameters": {}},
  {"statement": "MATCH (s:Session)-[:BY]->(p:Person) RETURN s.topic, p.name, toString(s.date) AS date ORDER BY s.date DESC LIMIT 5", "parameters": {}},
  {"statement": "MATCH (s:Spirit) RETURN s.name, s.type, s.status LIMIT 10", "parameters": {}}
]')

Read the full file on GitHub · 241 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. 9d ago First seen · 241 lines · 35 tokens per session scan A a70d74cac099

Subscribe to this mod's changes

summon is a skill published in the GitHub repository egregore-labs/egregore (282 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 2,728 once invoked, about $0.0002 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-30.