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/justinjdev/fellowship/questnpx skills add justinjdev/fellowship --skill questgit clone --depth 1 https://github.com/justinjdev/fellowshipWhat 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.00047 | $0.05663 |
| Opus 5 | $0.00023 | $0.02831 |
| Sonnet 5 | $0.00009 | $0.01133 |
| Haiku 4.5 | $0.00005 | $0.00566 |
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 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quest — Research, Plan, Implement
Overview
Orchestrates the full Research → Plan → Implement cycle with intentional compaction between phases. This is the hub skill that enforces context engineering discipline by invoking satellite skills at the right moments and maintaining hard gates between phases.
When to Use
- Any task that involves more than a quick fix
- When you want structured, disciplined progress through a complex change
- When context management matters (large codebase, multi-file changes)
Phase Flow
Phase 0: Onboard ──→ EnterWorktree → /council
│
▼
Phase 1: Research ──→ Explore agents / /gather-lore
│ Goal: understand the system, identify files
▼
/lembas
│
▼
Phase 2: Plan ──────→ Plan mode / writing-plans
│ Goal: explicit steps with file:line refs
▼
/lembas
│
▼
Phase 3: Implement ──→ TDD (test-driven-development) + execute plan
│ Goal: small verifiable changes via red-green-refactor
▼
/lembas
│
▼
Phase 3.5: Adversarial → balrog agent (edge cases, error paths, adversarial inputs)
│ Goal: find failure modes before review
▼
/lembas
│
▼
Phase 4: Review ─────→ /warden → /pr-review-toolkit:review-pr
│ → verification-before-completion
│ Goal: conventions + code quality + verified passing
▼
/lembas
│
▼
Phase 5: Complete ───→ finishing-a-development-branch
Goal: squash/merge, PR creation, cleanup
Process
External skill dependencies: Several steps invoke skills from the superpowers and pr-review-toolkit plugins (TDD, verification, branch finishing, PR review). If an invocation fails because the plugin is not installed, do not silently skip the step — perform the step's goal manually (write the failing test first yourself, run the verification commands yourself, review the diff yourself) and note the substitution in your phase output or gate message.
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 · 378 lines · 47 tokens per session scan A adfe1211c505
quest is a skill published in the GitHub repository justinjdev/fellowship (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 47 tokens to every session and 5,663 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-31.
Other skills, from other repositories
plan
Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request…
orbit
Running autonomous loops for nexus-autoloop. Generates script sets from goals, designs operation contracts, audits live loops, and recovers state — runners that complete reliably.
bond
Designing retention strategy, re-engagement, and churn prevention: retention analysis frameworks, re-engagement triggers, gamification, habit formation, and loyalty programs.
clause
Reviewing legal documents for Terms of Service, Privacy Policy, and Tokushoho compliance. Detects clause gaps and flags risks. Not a substitute for legal advice — consult a lawyer.
crest
Building engineer self-branding by turning technical contributions into a professional brand. Use for GitHub/LinkedIn/blog/conference positioning or content strategy.
grok
Designing regex, parsers, and DSLs for grammar authoring and ReDoS-safe regex. Not for REST APIs (Gateway) or DB schemas (Schema).