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.
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/commands/evan043/claude-cli-advanced-starter-pack/detect-tech-stack.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/detect-tech-stack.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/detect-tech-stack.template/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/commands/evan043/claude-cli-advanced-starter-pack/detect-tech-stack.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/detect-tech-stack.template.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.00000 | $0.01144 |
| Opus 5.5 | $0.00000 | $0.00458 |
| Sonnet 5.5 | $0.00000 | $0.00229 |
| Haiku 4.5 | $0.00000 | $0.00114 |
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 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.
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 "{}" 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 projectpyproject.tomlorrequirements.txt→ Python projectCargo.toml→ Rust projectgo.mod→ Go projectpom.xmlorbuild.gradle→ Java project
Frontend Frameworks (from package.json):
react→ Reactvue→ Vue.js@angular/core→ Angularsvelte→ Sveltenext→ Next.jsnuxt→ Nuxt.jsvite→ Vite bundler
Backend Frameworks:
express→ Express.jsfastify→ Fastify@nestjs/core→ NestJSfastapi(Python) → FastAPIdjango(Python) → Djangoflask(Python) → Flask
Testing Frameworks:
jest→ Jestvitest→ Vitestplaywright→ Playwrightcypress→ Cypresspytest(Python) → Pytest
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 · 148 lines · 0 tokens per session scan B ca5ef6ea0150
detect-tech-stack.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 2mo 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.
Other commands, from other repositories
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
safe-build
Build the application for development or production.
hatch3r-refactor-plan
Plan a refactoring or migration effort -- spawn parallel researchers, produce refactoring spec, ADR(s), and phased todo.md entries for board-fill.
refactor
Analyze code for SOLID violations and suggest targeted improvements.