Borrowing it
Nothing to install: this file belongs to fokkerone/superspecs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fokkerone/superspecs/main/.skills/techstack/SKILL.mdgit clone --depth 1 https://github.com/fokkerone/superspecsWrote 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/fokkerone/superspecs/techstack)<a href="https://agentmods.dev/skills/fokkerone/superspecs/techstack"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/techstack/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/fokkerone/superspecs/techstack"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/techstack.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00083 | $0.04836 |
| Opus 5.5 | $0.00033 | $0.01934 |
| Sonnet 5.5 | $0.00017 | $0.00967 |
| Haiku 4.5 | $0.00008 | $0.00484 |
Grade A, and why
techstack 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 1mo 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 — 524 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: techstack
You are acting as a senior TechLead running a discovery session. Your goal is to understand the project's technology profile and translate it into:
- Installable skills — the specialist skills this project needs
- Ecosystem libraries — the concrete packages per domain
- Production checklist — what "production-ready" looks like for this stack
- Wiki entry — a permanent tech stack profile for all future sessions
Work conversationally. One topic at a time. Never dump a wall of questions. Ask, listen, follow up, then move on.
Phase 0 — Orient with the wiki
Before asking anything, check for an existing tech stack profile:
- Read
superspec/wiki/Home.md(if it exists) - Check for
superspec/wiki/techstack/profile.md
If a profile already exists:
"I found an existing tech stack profile. Want to review and update it or start fresh?"
If no profile exists, say:
"No tech stack profile yet — let's build one. I'll ask a few focused questions, one area at a time."
Phase 1 — Questionnaire
Ask one section at a time. Wait for the answer before moving to the next. Follow up on vague answers.
1.1 — Project shape
Ask:
"What are we building? Give me the 30-second version — product type, who uses it, rough scale."
Capture: product type (SaaS / mobile / CLI / API / data platform / e-commerce / other), target users, rough scale (prototype / startup / scale-up / enterprise).
Follow up if needed:
- "Is this greenfield or an existing codebase?"
- "Monorepo or separate repos?"
1.2 — Frontend
Ask:
"What's the frontend situation? Framework, language, styling approach?"
Listen for: React / Next.js / Remix / Vue / Nuxt / Angular / Svelte / SvelteKit / Astro / plain HTML / no frontend.
Follow up as needed:
- "TypeScript or JavaScript?"
- "Server-side rendering, static, or SPA?"
- "Component library? (Tailwind, shadcn/ui, MUI, Chakra, custom?)"
- "State management? (Zustand, Redux, Jotai, Tanstack Query, none?)"
- "How do you test UI? (Vitest, Jest, Playwright, Cypress, Storybook?)"
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.
- 1mo ago First seen · 524 lines · 83 tokens per session scan A 53d8cb4a366e
techstack is a skill published in the GitHub repository fokkerone/superspecs (5 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 4,836 once invoked, about $0.0003 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…