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 skills add trtmn/agent-plugins --skill side-questgit clone --depth 1 https://github.com/trtmn/agent-pluginsWrote 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/trtmn/agent-plugins/side-quest)<a href="https://agentmods.dev/skills/trtmn/agent-plugins/side-quest"><img src="https://agentmods.dev/badge/skills/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/skills/trtmn/agent-plugins/side-quest"><img src="https://agentmods.dev/badge/skills/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.00161 | $0.02406 |
| Opus 5.5 | $0.00064 | $0.00962 |
| Sonnet 5.5 | $0.00032 | $0.00481 |
| Haiku 4.5 | $0.00016 | $0.00241 |
Grade B, and why
side-quest scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Run `/side-quest:setup` once after installing the plugin (or after updating it) — it delegates to the `side-quest-setup` agent, the single source of truth for what gets installed, and is idempotent — safe to re-run after How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First-time setup
Run /side-quest:setup once after installing the plugin (or after updating it) — it delegates to the side-quest-setup agent, the single source of truth for what gets installed, and is idempotent — safe to re-run after every plugin update. It deploys xp.sh, xp_core.py, xp-sync-daemon.sh, and statusline-command.sh to their stable paths; installs the cross-machine MQTT sync daemon; merges the statusLine block, the Stop hook, and the PostToolUse tick hook into ~/.claude/settings.json; and asks for approval before adding the ambient XP rule to ~/.claude/CLAUDE.md. See agents/side-quest-setup.md for exactly what each hook does and why.
The ledger at ~/.claude/side-quest/xp.json is shared between the stable copy and the plugin script.
Side Quest
Preflight check
Before doing anything else, check if setup has been run:
test -f "$HOME/.claude/side-quest/xp.sh"
If the file is missing, stop and tell the user:
"⚔️ The side-quest ledger isn't set up on this machine yet. Run
/side-quest:setupfirst — it deploys the XP scripts, configures the statusline, and walks you through the rest. (~2 minutes)"
Do not proceed with the quest until setup is confirmed.
If the file exists, continue normally.
Fire-and-forget task delegation with table-top flair. /side-quest <task> sends the work to background subagents and narrates the journey in D&D style — every themed response paired with a mandatory plain-English translation, so the flavor never costs you information.
How it works
-
Parse the quest. The command argument is the task. No argument → a one-line tavern-keeper prompt asks what quest you seek. Anything that needs user input (ambiguous targets, choices, credentials) gets resolved before launch — background agents can't ask questions mid-quest. Destructive or outward-facing quests (push, deploy, delete, send) are confirmed first.
-
Rate the Challenge Rating → 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
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 · 121 lines · 161 tokens per session scan B 9a81be87a7dc
side-quest is a skill published in the GitHub repository trtmn/agent-plugins (2 stars, last pushed 11d ago), licensed Unlicense. It adds 161 tokens to every session and 2,406 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…