detect-tech-stack.template

A technology-stack detector that examines a project and updates its configuration. A technology stack is the set of languages, frameworks, libraries, and tools used by an application.

In plain words
What is it for?
Use it to re-detect the stack and update the configuration used by agents, skills, and hooks.
Why use it?
It refreshes project information after dependencies, frameworks, or versions change.

Command

Install

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.

agentmods
npx agentmods add commands/evan043/claude-cli-advanced-starter-pack/detect-tech-stack.template
Clone the repo
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-pack
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,144 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01144
Opus 5 $0.00000 $0.00572
Sonnet 5 $0.00000 $0.00229
Haiku 4.5 $0.00000 $0.00114

Measured 2d ago against content hash ca5ef6ea0150, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

detect-tech-stack.template scanned grade B 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat .claude/config/tech-stack.json 2>/dev/null || echo "{}"
templates/commands/detect-tech-stack.template.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Codex Runtime Compatibility

This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:

  • AskUserQuestion => ask the user directly in chat.
  • WebSearch/WebFetch => use available web tools (search_query, open, find) and cite links.
  • Read/Write => use shell/filesystem tools in this workspace.
  • Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
  • Keep intent and output format identical; only adapt execution mechanics.

description: Re-run tech stack detection and update configuration

/detect-tech-stack - Tech Stack Analysis

Re-analyze the project's tech stack and update .claude/config/tech-stack.json.

Purpose

Issue #8: Tech stack detection previously only ran during terminal phase (ccasp init). This command allows re-running detection from within Claude CLI to:

  • Detect new dependencies added since initial setup
  • Update framework versions
  • Refresh configuration for agents, skills, and hooks

Execution Steps

Step 1: Read Current Tech Stack

cat .claude/config/tech-stack.json 2>/dev/null || echo "{}"

Save as previousStack for comparison.

Step 2: Detect Current Stack

Analyze the following files to build the new tech stack:

Package Managers:

  • package.json → Node.js/npm project
  • pyproject.toml or requirements.txt → Python project
  • Cargo.toml → Rust project
  • go.mod → Go project
  • pom.xml or build.gradle → Java project

Frontend Frameworks (from package.json):

  • react → React
  • vue → Vue.js
  • @angular/core → Angular
  • svelte → Svelte
  • next → Next.js
  • nuxt → Nuxt.js
  • vite → Vite bundler

Backend Frameworks:

  • express → Express.js
  • fastify → Fastify
  • @nestjs/core → NestJS
  • fastapi (Python) → FastAPI
  • django (Python) → Django
  • flask (Python) → Flask

Testing Frameworks:

  • jest → Jest
  • vitest → Vitest
  • playwright → Playwright
  • cypress → Cypress
  • pytest (Python) → Pytest

Read the full file on GitHub · 148 lines

Changes

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.

  1. 2d ago First seen · 148 lines · 0 tokens per session scan B ca5ef6ea0150

Subscribe to this mod's changes

detect-tech-stack.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,144 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.