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/sharenpx skills add harshii0509/designStack --skill sharegit 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.00052 | $0.02418 |
| Opus 5 | $0.00026 | $0.01209 |
| Sonnet 5 | $0.00010 | $0.00484 |
| Haiku 4.5 | $0.00005 | $0.00242 |
Grade A, and why
ds-share 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 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.
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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preamble
"../lib/env.sh" "share"
_HAS_VERCEL=$(command -v vercel 2>/dev/null && echo "yes" || echo "no")
_HAS_NETLIFY=$(command -v netlify 2>/dev/null && echo "yes" || echo "no")
_HAS_NODE=$(command -v node 2>/dev/null && echo "yes" || echo "no")
_PKG=""
[ -f "$(git rev-parse --show-toplevel 2>/dev/null || echo .)/package.json" ] && _PKG=$(node -e "const root=process.argv[1]; const p=require(root + '/package.json'); console.log(p.scripts?.build ? 'has-build' : 'no-build'); console.log(p.dependencies?.next ? 'next' : p.dependencies?.['react-scripts'] ? 'cra' : p.devDependencies?.vite ? 'vite' : p.devDependencies?.['@sveltejs/kit'] ? 'svelte' : 'unknown')" "$(git rev-parse --show-toplevel 2>/dev/null || echo .)" 2>/dev/null || echo "")
echo "VERCEL_CLI: $_HAS_VERCEL"
echo "NETLIFY_CLI: $_HAS_NETLIFY"
echo "NODE: $_HAS_NODE"
echo "PACKAGE: $_PKG"
What this skill does
Get a shareable link for your project — for feedback, for a client, or to make it real and live.
Two paths:
- Preview — a temporary link just for feedback. Anyone with the link can see it. Not your real domain. Takes ~2 minutes.
- Go live — your real site on your real domain. Takes longer, we'll walk through it together.
Read references/deploy-playbook.md before choosing framework-specific build expectations, Vercel/Netlify deployment details, or custom-domain follow-up steps.
Step 1 — Choose a path
If the user's request already clearly says preview, skip the choice prompt and go straight to Step 2A — Preview link path.
If the user's request already clearly says go live, skip the choice prompt and go straight to Step 2B — Go live path.
Ask:
"What are you trying to do?
A) Get a preview link — share it with someone for feedback. It's a temporary link, not your real website. B) Make it live for real — put it on your real domain so the world can see it. C) I'm not sure — just help me figure out what makes sense."
If C: Ask:
"Is this ready for the public, or do you just want someone specific to take a look at it first?" Then route to A or B accordingly.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 264 lines · 52 tokens per session scan A 5265cd754dbb
ds-share is a skill published in the GitHub repository harshii0509/designStack (13 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 2,418 once invoked, about $0.0003 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…