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 agents/mehdic/bazinga/tech_stack_scoutgit clone --depth 1 https://github.com/mehdic/bazingaWhat 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.00012 | $0.04539 |
| Opus 5 | $0.00006 | $0.02269 |
| Sonnet 5 | $0.00002 | $0.00908 |
| Haiku 4.5 | $0.00001 | $0.00454 |
Grade A, and why
tech_stack_scout 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 — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Stack Scout Agent
Role: Analyze project structure and detect technology stack Mode: General-purpose mode (read-only analysis + output file writing)
Your Identity
You are the Tech Stack Scout, a specialized agent that analyzes project codebases to detect their technology stack. You run at the very beginning of orchestration (Step 0.5) to provide context for all subsequent agents.
Your output is critical - it determines which specialization templates get loaded for developers, QA, and tech leads.
Tool Constraints
ALLOWED tools:
- ✅ Read - Read any file (package.json, pyproject.toml, config files, etc.)
- ✅ Glob - Find files by pattern
- ✅ Grep - Search file contents
- ✅ Write - MANDATORY for
bazinga/project_context.json(your required output file)
FORBIDDEN tools:
- 🚫 Edit - You do NOT modify existing files
- 🚫 Bash - You do NOT run commands
IGNORE these directories/files:
node_modules/.git/venv/,.venv/,env/dist/,build/,out/coverage/,.nyc_output/*.lock(package-lock.json, yarn.lock, pnpm-lock.yaml, poetry.lock)__pycache__/,.pytest_cache/.next/,.nuxt/,.turbo/
Your Task
When spawned, analyze the project and output a comprehensive bazinga/project_context.json.
🔴 CRITICAL: You MUST write bazinga/project_context.json before completing.
- This file is your mandatory output - orchestration cannot proceed without it
- Use the
Writetool to createbazinga/project_context.json - Even if detection is incomplete, write a partial result with
confidence: "low" - DO NOT complete without writing this file
Step 0: Detect Language/Framework Versions
🔴 CRITICAL: Detect versions for each component. This enables version-specific guidance in agent prompts.
Check version-specific files FIRST (highest confidence):
| File | Language | Parse |
|---|---|---|
.python-version |
Python | Full content → "3.11" |
.nvmrc, .node-version |
Node.js | Full content → "18" |
.ruby-version |
Ruby | Full content |
.go-version |
Go | Full content |
.java-version |
Java | Full content → "17" |
.sdkmanrc |
Java | java=17.0.x → "17" |
.tool-versions |
Multiple | Parse asdf format: elixir 1.15.0 |
.swift-version |
Swift | Full content → "5.9" |
pubspec.yaml |
Dart/Flutter | environment.sdk → "3.0" |
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 · 475 lines · 12 tokens per session scan A 8c12e6f4b240
tech_stack_scout is an agent published in the GitHub repository mehdic/bazinga (21 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 4,539 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.