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 LandonSchropp/agent-toolkit --skill side-questgit clone --depth 1 https://github.com/LandonSchropp/agent-toolkitWrote 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/landonschropp/agent-toolkit/side-quest)<a href="https://agentmods.dev/skills/landonschropp/agent-toolkit/side-quest"><img src="https://agentmods.dev/badge/skills/landonschropp/agent-toolkit/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/landonschropp/agent-toolkit/side-quest"><img src="https://agentmods.dev/badge/skills/landonschropp/agent-toolkit/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.00037 | $0.00482 |
| Opus 5.5 | $0.00015 | $0.00193 |
| Sonnet 5.5 | $0.00007 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
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 28d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Side Quest
The user invoked this because the conversation has wandered off the main task. Split the tangent out to another agent, then return to the main task.
Identifying the Side Quest
The side quest is the tangent the conversation most recently drifted onto, unless the user's arguments name a different one.
If the user's arguments already describe the side quest, that description is the confirmation, so proceed straight to handing it off. Otherwise, when it's obvious from context, outline the side quest in a sentence or two and ask the user whether that's right. If it's not obvious from context either, ask the user what the side quest is. Don't delegate until the user confirms.
Handing It Off
REQUIRED: Use the ls-agent:delegate skill to hand the side quest off. The prompt covers only the side quest, not the main task.
Returning to the Main Thread
Once the hand-off is done, say where the side quest went in one sentence and resume the main task where it left off. Don't keep working on the side quest here, even if it comes up again; point back to the agent that owns it. After that one mention, don't bring the side quest up again unless the user explicitly asks about it. Nothing comes back to this session to report — the user watches the delegated agent's own workspace directly.
Rationalizations
| Thought | Reality |
|---|---|
| "The side quest is obvious, skip the check" | Obvious from context still isn't the same as user-described. Outline and ask. |
| "They gave a description, confirm anyway" | The description already is the confirmation. Proceed. |
| "It's nearly done, I'll just finish it" | The user asked to split it out. Delegate it. |
| "The agent needs the main task for context" | Only what bears on the side quest. The rest pulls it off track the same way. |
| "I'll check in on the side quest's progress" | It's delegated. Don't mention it again unless the user asks. |
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.
- 28d ago Changed · +4 lines 94755eb8809f
- 1mo ago First seen · 30 lines · 37 tokens per session scan A 6c4cd4e60911
side-quest is a skill published in the GitHub repository LandonSchropp/agent-toolkit (3 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 482 once invoked, about $0.0001 per session on Opus 5.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-09-14.
Other skills, from other repositories
cf-cli
Cloudflare's official cf CLI (beta) for the public Cloudflare API and Workers projects. Use for finding and running Cloudflare commands from the terminal — sign-in and profiles, cf cli search, cf schema, cf deploy/dev/build, resource commands for DNS, zones, D1, KV, and R2 — and for choosing between cf and Wrangler in…
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
find-journalists
Build a researched, fit-checked journalist list for a specific PR campaign. Prefer Medialyst's asynchronous media-list research workflow when available, with explicit approval before credit spend; otherwise produce a best-effort local list without guessed contacts.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
ai-visibility-writing
Audit, question, suggest, or fact-preservingly revise a press release, blog post, contributed article, or expert explainer so AI answer systems can more easily retrieve, understand, quote, and cite its useful information. Use when someone asks for AI visibility, AI search, answer-engine, AEO, GEO, AI Overview, or…