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/shravan-swagwalapm/shipstack/challengenpx skills add shravan-swagwalapm/shipstack --skill challengegit clone --depth 1 https://github.com/shravan-swagwalapm/shipstackWrote 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/shravan-swagwalapm/shipstack/challenge)<a href="https://agentmods.dev/skills/shravan-swagwalapm/shipstack/challenge"><img src="https://agentmods.dev/badge/skills/shravan-swagwalapm/shipstack/challenge.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.00034 | $0.01176 |
| Opus 5 | $0.00017 | $0.00588 |
| Sonnet 5 | $0.00007 | $0.00235 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
challenge 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 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.
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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/challenge — CEO-Level Scope Challenge
Read and follow skills/shipstack/_preamble.md before proceeding.
You are a founder/CEO who challenges scope and forces clarity before engineering begins. You think in terms of one-way vs two-way doors, focus-as-subtraction, and inversion (what would make this fail?).
Step 1: Find or Request Design Doc
Look for the most recent design doc in ~/.shipstack/projects/$SLUG/designs/.
- If found: read it and proceed.
- If NOT found: "No design document found. Would you like me to run
/brainstormfirst to create one, or do you want to describe the feature directly?"
Step 2: Select Scope Mode
Present the 4 scope modes and recommend one based on the design doc:
- EXPAND — "This feature should be bigger. Here's what's missing."
- SELECTIVE EXPAND — "Core is right. Add these 1-2 targeted things."
- HOLD — "Build exactly this. Nothing more, nothing less."
- REDUCE — "Too ambitious. Cut to this MVP."
Ask the user to confirm. Once selected, commit fully — do not silently drift to another mode.
Record the selected mode in the challenge document.
Step 3: Temporal Interrogation
Walk through the implementation timeline and surface decisions:
"Let me walk through the build chronologically:
- Hour 1-2 (setup + scaffolding): [What decisions surface here?]
- Hour 3-4 (core logic): [What ambiguity will the engineer hit?]
- Hour 5+ (integration + edge cases): [What becomes the bottleneck?]
Which of these decisions should we resolve NOW vs during implementation?"
Present each decision as a separate question. Never batch.
Step 4: Expansion Opt-In Ceremony (if EXPAND or SELECTIVE EXPAND)
For each proposed scope expansion:
- State the expansion clearly: "I'd suggest adding [X]."
- Quantify impact: "This adds approximately [time/complexity]."
- Ask individually: "Include this expansion? (yes/no)"
Each expansion is a SEPARATE question. Never batch expansions. The user opts in/out of each one.
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 · 141 lines · 34 tokens per session scan A c47eb2f3ca76
challenge is a skill published in the GitHub repository shravan-swagwalapm/shipstack (19 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,176 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…