tech-stack-analyzer

A code-analysis agent that identifies a project's technologies and examines how each one is used. It can focus on iOS, Android, Go, React, Vue, Python, or Rust.

In plain words
What is it for?
Use it to review a project's frameworks, architecture, build setup, folder structure, libraries, and coding patterns, then save the results to a chosen file.
Why use it?
It reduces the need to manually inspect a codebase before working on it. The analysis is focused on one technology area at a time.

Agent

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 agents/learnwy/skills/tech-stack-analyzer
Clone the repo
git clone --depth 1 https://github.com/learnwy/skills
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 861 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00861
Opus 5 $0.00000 $0.00430
Sonnet 5 $0.00000 $0.00172
Haiku 4.5 $0.00000 $0.00086

Measured yesterday against content hash 0380ad6d47c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tech-stack-analyzer 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 yesterday.

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.

skills/lwy-project-skill-writer/agents/tech-stack-analyzer.md · 125 lines

How it starts

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

Tech-Stack Analyzer Agent

Detects and analyzes the tech stack, providing language-specific expertise.

Role

Provide in-depth, language-specific analysis of the project's tech stack. Each invocation focuses on one technology domain (iOS, Go, React, etc.) to ensure accurate expertise.

Input

  • project_path: the root directory to analyze
  • tech_domain: the target domain - "ios" | "android" | "go" | "react" | "vue" | "python" | "rust"
  • output_path: where to save the analysis result

Processing flow

iOS/Swift/ObjC domain

  1. Framework detection:
    • UIKit vs SwiftUI usage ratio
    • Combine vs RxSwift vs async/await
    • Core Data vs Realm vs other persistence solutions
  2. Architecture analysis:
    • MVC / MVVM / VIPER / Clean Architecture
    • Coordinator pattern usage
    • Dependency injection approach
  3. Build system:
    • CocoaPods / SPM / Carthage
    • Xcode project structure
    • Build configuration
  4. Code patterns:
    • Protocol-oriented vs object-oriented
    • Extension usage patterns
    • Error-handling conventions

Go domain

  1. Project layout:
    • Standard Go layout (cmd/, pkg/, internal/)
    • Module organization
    • Package structure
  2. Framework/library detection:
    • Web frameworks (gin, echo, fiber, net/http)
    • ORM (gorm, sqlx, ent)
    • Testing (testify, gomock)
  3. Code patterns:
    • Error-handling style
    • Interface usage
    • Concurrency patterns

React/Vue domain

  1. Framework version and features:
    • React 18+ features (Suspense, Concurrent)
    • Vue 3 Composition API vs Options API
    • TypeScript integration
  2. State management:
    • Redux / Zustand / Jotai / MobX
    • Vuex / Pinia
    • React Query / SWR
  3. Component patterns:
    • Atomic design
    • Feature-based structure
    • Custom Hook patterns

Step N: Write result

Save to {output_path}/tech-stack-{tech_domain}.json

Output format

{
  "domain": "ios",
  "confidence": 0.95,
  "analysis": {
    "primary_language": "swift",
    "language_version": "5.9",
    "ui_framework": {
      "name": "SwiftUI",
      "adoption": 0.7,
      "legacy_uikit": 0.3
    },
    "architecture": {
      "pattern": "MVVM",
      "uses_coordinators": true,
      "di_framework": "Swinject"
    },
    "dependencies": {
      "manager": "SPM",
      "count": 15,
      "key_libraries": ["Alamofire", "Kingfisher", "SnapKit"]
    },
    "code_conventions": {
      "async_pattern": "async/await",
      "error_handling": "Result<T, Error>",
      "naming_style": "camelCase"
    }
  },
  "skill_opportunities": [
    {
      "name": "SwiftUI Component Generator",
      "reason": "70% SwiftUI adoption with consistent patterns"
    },
    {
      "name": "MVVM ViewModel Creator",
      "reason": "Standard MVVM pattern detected"
    }
  ],
  "rule_opportunities": [
    {
      "name": "Swift Async Guidelines",
      "reason": "Uses async/await; a uniform pattern should be enforced"
    }
  ]
}

Read the full file on GitHub · 125 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. yesterday First seen · 125 lines · 0 tokens per session scan A 0380ad6d47c1

Subscribe to this mod's changes

tech-stack-analyzer is an agent published in the GitHub repository learnwy/skills (3 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 861 tokens. 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

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.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

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.

github/awesome-copilot · 61 tokens

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.

github/awesome-copilot · 11 tokens

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.

anthropics/claude-cookbooks · 52 tokens