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/quest/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/quest)<a href="https://agentmods.dev/skills/egregore-labs/egregore/quest"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/quest.svg" alt="Measured on agentmods" 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.00048 | $0.02387 |
| Opus 5 | $0.00024 | $0.01193 |
| Sonnet 5 | $0.00010 | $0.00477 |
| Haiku 4.5 | $0.00005 | $0.00239 |
Grade A, and why
quest 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 8d 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage quests — open-ended explorations that anyone can contribute to.
When to invoke
User says: "let's explore", "open question", "we should investigate", "start a quest", "what quests are open", "contribute to [quest]"
Not this: personal task → /todo · something is broken → /issue
Arguments: $ARGUMENTS (Optional: quest name, or subcommand)
Usage
/quest— List active quests/quest [name]— Show quest details and linked artifacts/quest new— Create a new quest interactively/quest contribute [name]— Add a contribution entry/quest prioritize [name] [high|medium|low|none]— Set quest priority/quest pause [name]— Pause a quest/quest complete [name]— Complete with outcome
Quest file location
All quests live in memory/quests/[slug].md
Quest frontmatter
---
title: Evaluation Benchmark for Dynamic Ontologies
slug: benchmark-eval
status: active | paused | completed
projects: [backend]
started: 2026-01-26
started_by: Alice
priority: 0
completed: null
---
Priority values: 0 (none/default), 1 (low), 2 (medium), 3 (high). Used by /activity scoring.
CRITICAL: Suppress raw output. Never show raw JSON to the user. All bin/graph.sh and bin/notify.sh calls MUST capture output in a variable and only show formatted status lines.
Mode detection
MODE=$(jq -r '.mode // "connected"' egregore.json 2>/dev/null)
Local mode (mode === "local"): Skip ALL bin/graph.sh and bin/notify.sh calls — do NOT run them. Do NOT show any graph-related messaging ("Graph offline", "Recording in knowledge graph", Neo4j, etc.). Create quest file in memory/quests/, update memory/quests/index.md, commit, push. No graph node creation, no notifications. Quest management works entirely from filesystem.
Specifically in local mode:
/quest new: Skip the Neo4j Quest creation section below. Show✓ Quest saved to memory/quests/{slug}.md(not "Quest node created")./quest pause/complete: Skip the Neo4j status update. Only update the quest markdown frontmatter./quest prioritize: Skip the Neo4j priority update. Only update the quest markdown frontmatter./quest [name]detail view: Skip the linked Todos graph query. Show quest details from the markdown file only. Omit the Todos section.- Notifications: Skip entirely — do not mention notifications.
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.
- 8d ago First seen · 290 lines · 48 tokens per session scan A a1b9879ac2cb
quest is a skill published in the GitHub repository egregore-labs/egregore (282 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 2,387 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.
Other skills, from other repositories
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
xiaohongshu-image-creator
An image-making assistant for Xiaohongshu, a Chinese social platform for lifestyle, product, and educational posts. It creates vertical covers and supporting images matched to the post’s topic, audience, and visual style.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…