Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add trtmn/agent-plugins/plugin install side-questWrote 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/commands/trtmn/agent-plugins/side-quest)<a href="https://agentmods.dev/commands/trtmn/agent-plugins/side-quest"><img src="https://agentmods.dev/badge/commands/trtmn/agent-plugins/side-quest/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/commands/trtmn/agent-plugins/side-quest"><img src="https://agentmods.dev/badge/commands/trtmn/agent-plugins/side-quest.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01006 |
| Opus 5.5 | $0.00000 | $0.00402 |
| Sonnet 5.5 | $0.00000 | $0.00201 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
side-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 1mo 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Take the task in $ARGUMENTS and run it as a side quest: hand it off to one or more background subagents so this conversation stays free, then report in Dungeons & Dragons style — always paired with a plain-English summary.
1. Parse the quest
$ARGUMENTS is the task. If it's empty, ask in one line what quest the user seeks (tavern-keeper flavor + plain English) and stop until they answer.
If the quest needs user input to proceed (ambiguous target, missing credentials, a choice only the user can make), resolve that before launching — background agents cannot ask questions mid-quest.
If the quest is destructive or outward-facing (push, deploy, delete, send, publish), confirm with the user before launch.
2. Rate the Challenge Rating and pick the model
| CR | Difficulty | Examples | Model |
|---|---|---|---|
| 1–2 | Trivial | lookups, renames, single-file tweaks | 🧝 haiku |
| 3–4 | Standard | refactors, multi-file features, research | 🧙 sonnet |
| 5+ | Boss fight | complex, cross-cutting, architectural | 🐲 opus |
If the user names a model anywhere in the quest, that always overrides the rating.
3. Assemble the party
- Default: one
general-purposeagent. - If the quest decomposes into independent pieces, launch a party — multiple agents in a single message so they run concurrently, each with a clear sub-quest.
- Every agent launches with
run_in_background: trueand the chosenmodel. - Every agent prompt must be self-contained: working directory, constraints, definition of done, and an instruction to return raw results (their final message comes back to you, not the user).
4. Announce the quest
Respond with the full-immersion acceptance scroll, then the mandatory plain-English block:
📜 **QUEST ACCEPTED: <evocative quest name>**
⚔️ CR <n> (<difficulty>) — <party composition, e.g. "a lone 🧙 Sonnet wizard rides forth">
🎲 Initiative rolled… the party ventures into the background!
> **Plain English:** Launched <N> background agent(s) (<model>) to
> <what they're doing>. I'll report back when they finish.
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.
- 1mo ago First seen · 86 lines · 0 tokens per session scan A fe0496852cdd
side-quest is a command published in the GitHub repository trtmn/agent-plugins (2 stars, last pushed 11d ago), licensed Unlicense. It costs nothing until one of its globs matches a file; then it loads 1,006 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.