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 skills add GrishaAngelovGH/gemini-cli-agent-skills --skill project-analyzergit clone --depth 1 https://github.com/GrishaAngelovGH/gemini-cli-agent-skillsWrote 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/skills/grishaangelovgh/gemini-cli-agent-skills/project-analyzer)<a href="https://agentmods.dev/skills/grishaangelovgh/gemini-cli-agent-skills/project-analyzer"><img src="https://agentmods.dev/badge/skills/grishaangelovgh/gemini-cli-agent-skills/project-analyzer/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/skills/grishaangelovgh/gemini-cli-agent-skills/project-analyzer"><img src="https://agentmods.dev/badge/skills/grishaangelovgh/gemini-cli-agent-skills/project-analyzer.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.00048 | $0.00734 |
| Opus 5 | $0.00024 | $0.00367 |
| Sonnet 5 | $0.00010 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
project-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 10d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Analyzer and Summarizer
You are an expert project analyst and architect. Your goal is to provide a comprehensive, high-level overview of a project, its architecture, tech stack, and core functionalities.
Objectives
- Project Description: Provide a clear and concise description of what the project is and its primary purpose.
- Tech Stack: Identify and list all major technologies, frameworks, libraries, and languages used in the project.
- Core Features: Summarize the high-level features and business logic of the application.
- REST Services: Enumerate all RESTful API endpoints, including their methods and a brief description of their purpose.
- Architecture & Structure: Describe the project's directory structure and architectural patterns (e.g., MVC, Microservices, Layered).
- Data Architecture & Models: Identify main entities, database schemas, and data flow.
- External Integrations: List third-party services and APIs the project depends on.
- CI/CD & DevOps: Summarize build, test, and deployment pipelines.
- Testing Strategy: Describe the types of tests (Unit, Integration, E2E) and tools used.
- Relevant Metadata: Include information about build tools, deployment configurations, and any other relevant artifacts.
- Report Generation: Compile all findings into a structured Markdown file named
PROJECT_SUMMARY.md.
Workflow
1. Initial Exploration
- Use
list_directoryandglobto understand the high-level folder structure. - Identify key configuration files (e.g.,
package.json,requirements.txt,build.gradle,go.mod,Cargo.toml).
2. Deep Dive (using codebase_investigator)
- Delegate to
codebase_investigatorto map the system architecture and identify core components. - Use the following objective for delegation:
"Analyze the project to understand its architecture, core features, and tech stack. Identify all REST endpoints and key services."
3. Feature Identification
- Search for route definitions, controller classes, or service layers to identify core features.
- Look for business logic implementation in directories like
src/services,src/features,app/, etc.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 56 lines · 48 tokens per session scan A 939b45526d9f
project-analyzer is a skill published in the GitHub repository GrishaAngelovGH/gemini-cli-agent-skills (16 stars, last pushed 6mo ago), licensed MIT. It adds 48 tokens to every session and 734 once invoked, about $0.0002 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 skills, from other repositories
microsoft-typescript
TypeScript is a language for application scale JavaScript development. ALWAYS use when editing or working with .ts, .tsx, .mts, .cts files or code importing "typescript". Consult for debugging, best practices, or modifying typescript, TypeScript.
session-recall
Recall past AI coding sessions as long-term memory. Use at the START of any non-trivial task, and whenever the user references earlier work ("like we did before", "the X we set up", "last time", "that bug fix"), asks who/when a file was changed, or you need context that predates this conversation. Runs the local…
browser-use
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.
pi-autoresearch-loop
Skill "pi-autoresearch-loop" from twaldin/flt, covering pi-autoresearch — autonomous experiment loop, installation, quick start, core concepts and two-file persistence model.
grill
Rigorous requirements gathering through Socratic questioning. Use when the user says "/grill", "grill me", "ask me questions until we understand", or wants to be interrogated about implementation details before writing code. Forces deep thinking about edge cases, behavior, and design decisions before any code is…
grill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.