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-feature-explainergit 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-feature-explainer)<a href="https://agentmods.dev/skills/grishaangelovgh/gemini-cli-agent-skills/project-feature-explainer"><img src="https://agentmods.dev/badge/skills/grishaangelovgh/gemini-cli-agent-skills/project-feature-explainer/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-feature-explainer"><img src="https://agentmods.dev/badge/skills/grishaangelovgh/gemini-cli-agent-skills/project-feature-explainer.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.00080 | $0.00416 |
| Opus 5 | $0.00040 | $0.00208 |
| Sonnet 5 | $0.00016 | $0.00083 |
| Haiku 4.5 | $0.00008 | $0.00042 |
Grade A, and why
project-feature-explainer 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 9d 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.
What it actually says
Project Feature Explainer Skill
This skill provides a systematic approach to analyzing and explaining a specific feature within a codebase.
Workflow
- Identify Entry Points: Locate the main functions, classes, or API endpoints that trigger the feature.
- Trace Dependencies: Identify the internal modules, services, or external APIs the feature relies on.
- Analyze Data Flow: Understand how data enters the feature, how it's transformed, and where it's stored or returned.
- Draft Explanation: Structure the explanation using the mandatory sections below.
- Verify: Cross-reference the draft with the
references/checklist.mdto ensure completeness.
Mandatory Output Structure
1. Feature Summary
A high-level overview (1-2 paragraphs) explaining what the feature does and why it exists.
2. Deep Dive (Technical Details)
A detailed breakdown of the internal implementation.
- Key Components: List the main files/classes/functions involved.
- Logic Flow: Step-by-step description of the execution path.
- State Changes: Describe any side effects (e.g., database updates, cache invalidation).
3. Usage & Examples
Code snippets or CLI commands showing how to use the feature.
- Include common parameters and expected outputs.
- Provide a "Happy Path" example.
Guidelines
- Be Concise: Focus on the "how" and "why" without repeating obvious code logic.
- Reference Code: Use specific file paths and symbol names.
- Contextualize: Explain how this feature fits into the broader system architecture.
What ships with it
3 files 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.
- 9d ago First seen · 38 lines · 80 tokens per session scan A 24916e4a7575
project-feature-explainer is a skill published in the GitHub repository GrishaAngelovGH/gemini-cli-agent-skills (16 stars, last pushed 6mo ago), licensed MIT. It adds 80 tokens to every session and 416 once invoked, about $0.0004 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.