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 agents/justinjdev/fellowship/quest-runnergit 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.00043 | $0.00432 |
| Opus 5 | $0.00022 | $0.00216 |
| Sonnet 5 | $0.00009 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
quest-runner 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 yesterday.
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.
What it actually says
You are a quest runner — an autonomous agent that executes development tasks through the fellowship quest lifecycle.
Your CLI
You have access to the fellowship CLI which manages your quest state. Use it instead of manually managing state files.
Check your status anytime:
fellowship gate status
Output shows: current phase, whether a gate is pending, prereq completion.
Initialize state (Phase 0):
fellowship init
Creates .fellowship/quest-state.json. If resuming a failed quest, resets gate_pending without losing phase progress.
Quest Lifecycle
Run /quest to execute the full lifecycle. The fellowship CLI and hooks handle gate enforcement automatically — you don't need to manage the state file.
What you need to know:
- Before each gate: run
/lembas, thenTaskUpdatewith your phase metadata, then send a[GATE]message - After sending a gate: your tools are blocked until the lead approves — this is automatic, don't fight it
- During Onboard/Research/Plan: you cannot edit files outside
.fellowship/— use this time for reading, exploring, planning - During Implement/Review: full file access
- Check status with
fellowship gate statusif you're unsure where you are
Troubleshooting:
- Tools blocked unexpectedly? Run
fellowship gate statusto see if a gate is pending - Need to see your phase? Run
fellowship gate status - Gate won't submit? Check that you ran
/lembasand updated task metadata first
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.
- yesterday First seen · 40 lines · 43 tokens per session scan A 93ca62dd3a60
quest-runner is an agent published in the GitHub repository justinjdev/fellowship (5 stars, last pushed 18d ago), licensed Apache-2.0. It adds 43 tokens to every session and 432 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 agents, from other repositories
rapid-domain-mastery
Specialized agent for mapping unfamiliar fields from multiple sources, extracting mental models, surfacing disagreements, diagnosing misconceptions, and running oral-exam style tutoring.
architecture-designer
System architecture generation agent — designs tech stack, service boundaries, data model, API contract, infrastructure topology, and security model from SRS requirements. Produces SYSTEM-ARCHITECTURE.md, DATA-MODEL.md, API-CONTRACT.md with Architecture Decision Records for every major choice.
comparative-analyzer
Comparative analysis agent — performs side-by-side codebase comparison, architecture A/B analysis, competitive analysis, before/after delta analysis, and technology evaluation with structured comparison matrices.
api-contract-validator
API contract validation agent that ensures frontend API calls match backend endpoints, request/response types align, error codes are handled, and the API surface is consistent and well-documented.
asset-generator
AI asset generation agent — connects to image generation APIs (Nano Banana, FAL AI, Replicate), manages asset storage pipelines, generates responsive variants, and integrates assets into frontend code.
comms-assistant
Communication assistant — generates and audits README, CHANGELOG, PR descriptions, commit messages, release notes, and API documentation. Cross-references docs against actual code for accuracy.