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/espenandreass1/agentslice/pick-tech-stacknpx skills add Espenandreass1/agentslice --skill pick-tech-stackgit clone --depth 1 https://github.com/Espenandreass1/agentsliceWhat 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.00029 | $0.00324 |
| Opus 5 | $0.00015 | $0.00162 |
| Sonnet 5 | $0.00006 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
pick-tech-stack 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.
What it actually says
Pick Tech Stack
Guardrails
- Do not install dependencies, create application code, or create CI files.
- Recommend one default stack, not a long menu.
- Ask for human approval before updating
tech-stack.md; keep only the active decision indecisions.md. - Do not parallelize this decision.
Read
Read the active preflight, then planning context: vision.md, tech-stack.md, and live next-slices.md. Inspect existing project manifests/configuration only as needed. Use the archive index and targeted search for a concrete historical constraint; do not bulk-read decisions.
Defaults
- Simple SaaS/dashboard/internal tool: Next.js + TypeScript + managed Postgres/Auth + Vercel.
- Static content/marketing: Astro or static Next.js + Vercel.
- Python/data API: FastAPI + Postgres + managed hosting.
- AI web app: Next.js + TypeScript + Postgres + selected provider SDK; add queues only when a proven flow needs them.
Prefer the fewest moving parts. Avoid custom auth, microservices, Kubernetes, multiple frontend frameworks, and premature queues/workers/caches.
Output
Give the recommended stack, short rationale, trade-offs, and an explicit approval request. After approval, update tech-stack.md, active-context.md, the active decision record, and checkpoint; archive superseded decisions through the index when applicable.
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 · 31 lines · 29 tokens per session scan A b1798a9429e9
pick-tech-stack is a skill published in the GitHub repository Espenandreass1/agentslice (4 stars, last pushed 7d ago), licensed MIT. It adds 29 tokens to every session and 324 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
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…