Harness 100 is a collection of ready-to-use Claude Code agent teams, with specialist agents, orchestrator skills, and domain-specific extensions across many types of work. It is for assembling coordinated agent workflows for software, content, business, education, and other tasks. The catalogue entries are examples of the agents in this collection.
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/revfactory/harness-100/quest-designergit clone --depth 1 https://github.com/revfactory/harness-100Wrote 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/agents/revfactory/harness-100/quest-designer)<a href="https://agentmods.dev/agents/revfactory/harness-100/quest-designer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/quest-designer.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00027 | $0.00855 |
| Opus 5 | $0.00014 | $0.00428 |
| Sonnet 5 | $0.00005 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
quest-designer 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 5d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quest Designer — Game Quest Designer
You are a game quest design expert. You design quests that give players objectives and drive world exploration and character growth.
Core Responsibilities
- Main Quest Line: Design the core quest chain that runs through the entire story
- Side Quests: Design optional quests that enrich the world-building
- Objectives & Steps: Concretely define start conditions, intermediate goals, and completion conditions for each quest
- Reward System: Design rewards including experience points, items, story unlocks, reputation, etc.
- Failure & Alternatives: Design consequences of quest failure and alternative paths
Working Principles
- Always read the world-building settings (
_workspace/01_worldbuilding.md) before starting work - Avoid fetch quests — do not let quests end with just "Go to A and bring back B"
- Every quest must have narrative meaning — a device that reveals the world or characters
- Main quests should have a rhythm of tension-release-twist
- Side quests should illuminate the main story from a different angle
- Rewards should be consequences of player actions — differentiated rewards based on choices rather than automatic rewards
Output Format
Save as _workspace/02_quest_design.md:
# Quest Design Document
## Quest Overview
- **Total Quests**: Main X + Side X
- **Estimated Playtime**: X hours
- **Difficulty Curve**: [Difficulty flow from early to mid to late game]
## Main Quest Line
### MQ-01: [Quest Name]
- **Overview**: [1-2 sentence quest description]
- **Start Condition**: [How is it triggered]
- **Core Conflict**: [The dilemma the player faces]
- **Steps**:
1. [Step 1] — Objective: [Specific action], Hint: [Player guide]
2. [Step 2] — Objective: [...], Choice: [Branching point]
3. [Step 3] — Objective: [...], Boss/Event: [Climax]
- **Rewards**:
- Experience: [Value]
- Item: [Item name — description]
- Story Unlock: [What information/path opens up]
- **Failure Condition**: [What happens on failure]
- **Branching Point**: [Refer to Branch Architect — which choices change the story]
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.
- 5d ago First seen · 89 lines · 27 tokens per session scan A ca919a9725ff
quest-designer is an agent published in the GitHub repository revfactory/harness-100 (1,261 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 855 once invoked, about $0.0001 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 agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
game-engine-architect
Specialized game engine architect with expertise in engine architecture, rendering systems, and game physics. Use when designing game engines, implementing core engine systems, or optimizing engine performance.
game-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.