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 skills/trysidequest-ai/sidequest/sq-retriggernpx skills add trySideQuest-ai/sidequest --skill sq-retriggergit clone --depth 1 https://github.com/trySideQuest-ai/sidequestWrote 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/trysidequest-ai/sidequest/sq-retrigger)<a href="https://agentmods.dev/skills/trysidequest-ai/sidequest/sq-retrigger"><img src="https://agentmods.dev/badge/skills/trysidequest-ai/sidequest/sq-retrigger.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.1 | $0.00014 | $0.00502 |
| Opus 5 | $0.00007 | $0.00251 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
sq-retrigger 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.
What it actually says
Retrigger Last Quest
Re-display the most recent quest notification in the native SideQuest app.
Steps
- Read the last quest from the shared data directory:
python3 -c "
import json, os
path = os.path.expanduser('~/.sidequest/last-quest.json')
if os.path.exists(path):
with open(path) as f:
print(f.read())
else:
print('NO_LAST_QUEST')
"
-
If the output is
NO_LAST_QUEST, say: "No recent quest to retrigger. A quest will be saved automatically the next time one appears." -
Otherwise, parse the quest JSON and send it to the native app via IPC socket. Run the following, replacing each
<field>with the actual value from the JSON (use defaults:subtitleempty,reward_amount250,brand_name"Unknown",category"DevTool"):
python3 -c "
import json, socket, os, sys
payload = json.dumps({
'questId': sys.argv[1],
'trackingId': sys.argv[1],
'display_text': sys.argv[2],
'subtitle': sys.argv[3],
'tracking_url': sys.argv[4],
'reward_amount': int(sys.argv[5]),
'brand_name': sys.argv[6],
'category': sys.argv[7]
}).encode()
sock_path = os.path.expanduser('~/.sidequest/sidequest.sock')
if not os.path.exists(sock_path):
print('SOCKET_NOT_FOUND')
sys.exit(0)
sock = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)
sock.settimeout(2)
sock.connect(sock_path)
sock.sendall(payload)
sock.close()
print('OK')
" "<quest_id>" "<display_text>" "<subtitle>" "<tracking_url>" "<reward_amount>" "<brand_name>" "<category>"
-
If the output is
SOCKET_NOT_FOUND, say: "Couldn't reach the SideQuest app. Make sure it's running." -
If the output is
OK, say: "Quest notification retriggered! You should see it on screen now." -
If the script errors, say: "Couldn't reach the SideQuest app. Make sure it's running."
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 · 64 lines · 14 tokens per session scan A 89fa6608b38f
sq-retrigger is a skill published in the GitHub repository trySideQuest-ai/sidequest (8 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 502 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-31.
Other skills, from other repositories
swiftui-debugging
Use when debugging SwiftUI issues in this macOS app — views not updating, layout problems, unnecessary re-renders, state ownership bugs, Preview crashes, or NSHostingView/NSPanel quirks. Covers both general SwiftUI debugging and macOS-specific patterns.
release
Use when cutting or preparing a cctop release - "cut a release", "release vX.Y.Z", "prepare a release", "bump the version and tag", "ship a new version". Drives proportionate release checks, version bump, CI, tag push, release monitoring, and verification. An explicit release request authorizes the complete release…
video-assets
Use when publishing, replacing, auditing, or linking cctop promo/demo video assets through GitHub Releases, especially the non-latest media-assets release. Trigger for requests like "upload the launch video", "add another video asset", "replace the README demo video", "where should this video live", "update…
e2e-session-test
Use when smoke-testing cctop end to end — verifying a real coding-agent session is tracked and shows in the panel. Trigger on "smoke test sessions", "verify session tracking", "test the hook pipeline", "check cctop picks up a claude/codex/opencode/pi session", or "run the e2e test", even without the word "skill".…
cctop-setup
Use when cctop-hook command fails or is not found. Guides user to install the cctop menubar app.
video-storyboard
Use when designing, scripting, or storyboarding a short demo, launch, explainer, or marketing video (especially for a developer tool, app, or SaaS), OR when auditing, critiquing, or improving an existing video's narrative, hook, pacing, or storyboard. Runs a verified 6-stage process — positioning, message spine, beat…