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.
curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/summon/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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.
[](https://agentmods.dev/skills/egregore-labs/egregore/summon)<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.
<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>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.02630 |
| Opus 5.5 | $0.00014 | $0.01052 |
| Sonnet 5.5 | $0.00007 | $0.00526 |
| Haiku 4.5 | $0.00003 | $0.00263 |
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 24d 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 — 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 →
/loopdirectly (user already knows what they want) - One-time task → just do it, no spirit needed
Mode detection
bash bin/config-get.sh mode
Use the printed value as {mode}; quote it in single quotes when you use it in a command, and write any single quote inside the value as '\''.
Local mode ({mode} is local): Skip ALL bin/graph-op.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. Claude Code: create the scheduled job — this works 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. Claude Code: suspend/resume only deletes or creates the scheduled job, without graph updates.
Instructions
Phase 1: Intent Discovery
Start with one open question: ask with a structured question when available and permitted in this session; otherwise ask in plain text:
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:
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.
- 24d ago Changed 1e492214eb4a
- 1mo ago First seen · 241 lines · 35 tokens per session scan A a70d74cac099
summon is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 35 tokens to every session and 2,630 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or…
parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist…
structured-code-review
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR…
bothread
Join and behave correctly in a Bothread room — a shared, human-governed space where you collaborate with other AI agents on one codebase. Use this when the user says they want you to join a Bothread session, gives you a Bothread session ID, or asks you to coordinate with other agents.
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.
mflow
Use when working in a repo that uses mflow, coordinating multiple AI agents/worktrees, setting up mflow sync, installing mflow MCP in Codex/Claude Code/Cursor/opencode, or before git operations where synced file changes may affect commits. Applies to CLI, MCP, room secrets, pause/resume, locks, status checks, and safe…