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/harshii0509/designstack/upgradenpx skills add harshii0509/designStack --skill upgradegit clone --depth 1 https://github.com/harshii0509/designStackWhat 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.00067 | $0.01730 |
| Opus 5 | $0.00034 | $0.00865 |
| Sonnet 5 | $0.00013 | $0.00346 |
| Haiku 4.5 | $0.00007 | $0.00173 |
Grade A, and why
ds-upgrade 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 2d 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.
echo "ERROR: No git install at $INSTALL_DIR — reinstall with the curl command from the README." How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ds-upgrade — Update designStack
Keep users on the latest designStack with the same flow as the root skill’s update check.
Inline upgrade flow (from root /ds preamble)
When root SKILL.md printed UPGRADE_AVAILABLE <old> <new> from ds-update-check, read this file and run Step 1 before continuing to the sub-skill the user asked for.
Step 1: Auto-upgrade or ask
Resolve auto-upgrade:
_AUTO=""
[ "${DS_AUTO_UPGRADE:-}" = "1" ] && _AUTO="true"
if [ -z "$_AUTO" ] && [ -f "$HOME/.dstack/config.yaml" ]; then
if grep -qiE '^[[:space:]]*auto_upgrade:[[:space:]]*true' "$HOME/.dstack/config.yaml" 2>/dev/null; then
_AUTO="true"
fi
fi
echo "AUTO_UPGRADE=${_AUTO:-false}"
If AUTO_UPGRADE=true: Skip AskUserQuestion. Tell the user you're auto-upgrading designStack v{old} → v{new}, then go to Step 2. If the update script fails, say auto-upgrade failed and suggest running /ds-upgrade manually.
Else use AskUserQuestion:
- Question: "designStack v{new} is available (you're on v{old}). Upgrade now?"
- Options:
["Yes, upgrade now", "Always keep me up to date", "Not now", "Never ask again"]
"Yes, upgrade now" → Step 2
"Always keep me up to date":
mkdir -p "$HOME/.dstack"
_CFG="$HOME/.dstack/config.yaml"
if [ ! -f "$_CFG" ]; then
echo "update_check: true" > "$_CFG"
echo "auto_upgrade: true" >> "$_CFG"
else
if grep -qiE '^[[:space:]]*auto_upgrade:' "$_CFG" 2>/dev/null; then
sed -i.bak 's/^[[:space:]]*auto_upgrade:.*/auto_upgrade: true/' "$_CFG" 2>/dev/null || \
perl -i -pe 's/^\s*auto_upgrade:.*/auto_upgrade: true/' "$_CFG" 2>/dev/null || true
else
echo "auto_upgrade: true" >> "$_CFG"
fi
rm -f "$_CFG.bak" 2>/dev/null || true
fi
Say: "Auto-upgrade is on — future releases will install without asking." Then Step 2.
"Not now": Write snooze (same version escalation as gstack):
_SNOOZE_FILE="$HOME/.dstack/update-snoozed"
_REMOTE_VER="{new}"
_CUR_LEVEL=0
if [ -f "$_SNOOZE_FILE" ]; then
_SNOOZED_VER=$(awk '{print $1}' "$_SNOOZE_FILE")
if [ "$_SNOOZED_VER" = "$_REMOTE_VER" ]; then
_CUR_LEVEL=$(awk '{print $2}' "$_SNOOZE_FILE")
case "$_CUR_LEVEL" in *[!0-9]*) _CUR_LEVEL=0 ;; esac
fi
fi
_NEW_LEVEL=$((_CUR_LEVEL + 1))
[ "$_NEW_LEVEL" -gt 3 ] && _NEW_LEVEL=3
echo "$_REMOTE_VER $_NEW_LEVEL $(date +%s)" > "$_SNOOZE_FILE"
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.
- 2d ago First seen · 168 lines · 67 tokens per session scan A eb525caa18b3
ds-upgrade is a skill published in the GitHub repository harshii0509/designStack (13 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 1,730 once invoked, about $0.0003 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-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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…