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-statusnpx skills add trySideQuest-ai/sidequest --skill sq-statusgit 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-status)<a href="https://agentmods.dev/skills/trysidequest-ai/sidequest/sq-status"><img src="https://agentmods.dev/badge/skills/trysidequest-ai/sidequest/sq-status.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.00079 | $0.01497 |
| Opus 5 | $0.00039 | $0.00749 |
| Sonnet 5 | $0.00016 | $0.00299 |
| Haiku 4.5 | $0.00008 | $0.00150 |
Grade A, and why
sq-status scanned grade A 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s --max-time 3 https://api.trysidequest.ai/health && echo "OK" || echo "FAILED" How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sidequest:sq-status
Comprehensive health check for SideQuest.
Steps
Perform these checks in order and collect the results:
1. Authentication Status
Read the config file:
cat ~/.sidequest/config.json | python3 -c "
import sys, json
try:
config = json.load(sys.stdin)
token = config.get('token')
if token:
print('OK')
else:
print('NO_TOKEN')
except:
print('NO_CONFIG')
"
-
If output is
NO_TOKEN: Auth status = "Not authenticated"- Add advice: "Run /sidequest:sq-login to authenticate."
-
If output is
NO_CONFIG: Auth status = "Not configured"- Add advice: "Run /sidequest:sq-login to set up SideQuest."
-
If output is
OK: Auth status = "Authenticated"
2. Native App Status
Test socket connection to the native app:
echo "" | nc -U -w1 ~/.sidequest/sidequest.sock 2>/dev/null && echo "RUNNING" || echo "NOT_RUNNING"
- If output is
RUNNING: Native App status = "Running (socket connected)" - If output is
NOT_RUNNING: Native App status = "NOT RUNNING"- Add advice: "Quests can't be delivered. Run: open ~/Applications/SideQuestApp.app"
3. API Health
Test connectivity to the API:
curl -s --max-time 3 https://api.trysidequest.ai/health && echo "OK" || echo "FAILED"
- If output contains
OK: API status = "Healthy" - If output is
FAILED: API status = "Unreachable"- Add advice: "Check your internet connection."
4. Last Quest Timing
Read timing state:
cat ~/.sidequest/timing-state.json 2>/dev/null | python3 -c "
import sys, json, time
try:
data = json.load(sys.stdin)
last_quest = data.get('last_quest_shown', 0)
daily_count = data.get('daily_quest_count', 0)
if last_quest:
print(f'OK:{last_quest}:{daily_count}')
else:
print('NEVER')
except:
print('NO_TIMING')
"
- If output is
NO_TIMINGorNEVER: Last Quest = "Never"- Add: "Your first quest will appear after a git commit or 10-minute coding gap."
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.
- 4d ago First seen · 206 lines · 79 tokens per session scan A 6a4b1ee0f96c
sq-status is a skill published in the GitHub repository trySideQuest-ai/sidequest (8 stars, last pushed 4mo ago), licensed MIT. It adds 79 tokens to every session and 1,497 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…