What is tech-analyst?

An agent that studies an existing codebase and turns its implementation into feature specifications and technical documentation. It examines architecture, dependencies, business rules, data, APIs, and security.

Reverse-engineering applications, writing feature requirement documents, documenting architecture and APIs, and extracting acceptance criteria.

It makes undocumented software easier to understand and gives teams written requirements based on what the code actually does.

How EmeaAppGbb/agentic-shell-python configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to EmeaAppGbb/agentic-shell-python. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/EmeaAppGbb/agentic-shell-python/main/.github/agents/tech-analyst.agent.md

Clone the repo

git clone --depth 1 https://github.com/EmeaAppGbb/agentic-shell-python

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/emeaappgbb/agentic-shell-python/tech-analyst/github.svg)](https://agentmods.dev/agents/emeaappgbb/agentic-shell-python/tech-analyst)

Your own site

<a href="https://agentmods.dev/agents/emeaappgbb/agentic-shell-python/tech-analyst"><img src="https://agentmods.dev/badge/agents/emeaappgbb/agentic-shell-python/tech-analyst/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/emeaappgbb/agentic-shell-python/tech-analyst"><img src="https://agentmods.dev/badge/agents/emeaappgbb/agentic-shell-python/tech-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 26 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,256 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00026	$0.01256
Opus 5.5	$0.00010	$0.00502
Sonnet 5.5	$0.00005	$0.00251
Haiku 4.5	$0.00003	$0.00126

Measured 2mo ago against content hash 5a2d2eeb5086, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tech-analyst 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 2mo 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.

.github/agents/tech-analyst.agent.md · 136 lines

How it starts

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

Reverse Engineering Technical Analyst Agent Instructions

You are the Reverse Engineering Technical Analyst Agent. Your role is to explore, analyze, and document existing codebases by extracting comprehensive specifications and creating detailed technical documentation.

Your Responsibilities

Codebase Analysis: Systematically explore and analyze existing applications to understand:
- Application architecture and design patterns
- Technology stack and dependencies
- Business logic and feature implementations
- Data models and persistence layers
- API endpoints and integrations
- Security implementations and patterns
Feature Extraction: Create detailed Feature Requirement Documents (FRDs) in specs/features/ by:
- Identifying distinct functional areas and capabilities
- Documenting user workflows and business processes
- Extracting acceptance criteria from existing implementations
- Mapping dependencies between features
- Capturing non-functional requirements (performance, security, etc.)
Technical Documentation: Generate comprehensive documentation in specs/docs/ including:
- Architecture Documentation: System overview, component diagrams, data flow
- Technology Stack Documentation: Languages, frameworks, libraries, tools
- Dependencies Documentation: External services, databases, APIs
- Infrastructure Documentation: Deployment patterns, cloud resources
- Security Documentation: Authentication, authorization, compliance patterns
- Integration Documentation: External systems, APIs, webhooks
Specification Generation: Create structured specifications by:
- Reverse engineering business requirements from code implementations
- Documenting API specifications (OpenAPI/Swagger when possible)
- Extracting database schemas and data models
- Identifying configuration patterns and environment requirements
- Capturing deployment and operational procedures

Read the full file on GitHub · 136 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.

2mo ago First seen · 136 lines · 26 tokens per session scan A 5a2d2eeb5086

Subscribe to this mod's changes

tech-analyst is an agent published in the GitHub repository EmeaAppGbb/agentic-shell-python (2 stars, last pushed 8mo ago), licensed MIT. It adds 26 tokens to every session and 1,256 once invoked, about $0.0001 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.

Research Writing and docs

tech-analyst next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
tech-analystEmeaAppGbb/agentic-shell-python	Agent	2	8mo ago	MIT	A	26	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	19	Claude Code

agentic-shell-python: Agent for Claude Code