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 qte77/claude-code-plugins --skill analyzing-source-projectgit clone --depth 1 https://github.com/qte77/claude-code-pluginsWrote 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/qte77/claude-code-plugins/analyzing-source-project)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/analyzing-source-project"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/analyzing-source-project/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/qte77/claude-code-plugins/analyzing-source-project"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/analyzing-source-project.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.00044 | $0.00664 |
| Opus 5.5 | $0.00018 | $0.00266 |
| Sonnet 5.5 | $0.00009 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
analyzing-source-project 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 17d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyzing Source Project (Phase 0)
Target: $ARGUMENTS
Phase 0 of the GTM pipeline. Produces a technical capability profile of the source project that feeds Phase 1B (researching-market).
Mode Awareness
Read config/mode.md before starting:
concise— Bullet summaries, 3-5 points per sectiondetailed— Full narrative with evidence and code referencesconservative— Focus on proven, documented capabilitiesambitious— Highlight unrealized potential and extension opportunities
Inputs
config/sources.md— Source projects to analyzeconfig/comments_research.md— Research constraints and focus areasconfig/mode.md— Style and approach settings
Workflow
- Identify source projects from
config/sources.md - Clone or fetch the repository if a URL is provided (use WebFetch for public repos)
- Assess architecture — Directory structure, module boundaries, design patterns
- Inventory tech stack — Languages, frameworks, dependencies, infrastructure hints
- Extract differentiators — What does this project do unusually well?
- Identify limitations — Scalability ceilings, missing features, tech debt signals
- Rate capabilities — Score each capability area (1-5) with rationale
- Validate against criteria — Check
config/validation_criteria.mdPhase 0 gates
Output
Write to results/phase-0/:
capability-profile.md
# Source Project Capability Profile
## Project: [name]
## Architecture Summary
[Overview of system design and key components]
## Tech Stack
- Language: [language + version]
- Framework: [framework]
- Key dependencies: [list]
## Differentiating Capabilities
1. [Capability] — Score: [1-5] — Evidence: [file/feature reference]
2. ...
## Limitations and Risks
- [Limitation] — Impact: [High/Medium/Low]
## GTM-Relevant Technical Signals
[How technical characteristics translate to market positioning opportunities]
Rules
- Ground every capability claim in observable code or documentation evidence
- Distinguish between current state and aspirational/roadmap features
- Limitations are as important as strengths for honest PMF assessment
- Cross-reference with
config/comments_research.mdscope constraints
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.
- 17d ago Changed · +1 lines 3b53ca5868a7
- 21d ago Changed · +1 lines 8e92c362e64c
- 1mo ago First seen · 79 lines · 44 tokens per session scan A 5e92cfcb7b8a
analyzing-source-project is a skill published in the GitHub repository qte77/claude-code-plugins (3 stars, last pushed 4d ago), licensed Apache-2.0. It adds 44 tokens to every session and 664 once invoked, about $0.0002 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.
Other skills, from other repositories
android-kotlin-compose
Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…
android-kotlin-coroutines
Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…
codex-advisor
Advisory consultation skill for architectural reviews, design decisions, code analysis, and technology evaluation. Codex provides recommendations without making code changes. Invoked by phrases like "consult Codex", "get Codex's opinion", "ask Codex about", "have Codex review", "Codex analysis", "validate this…
ast-grep
Structural code search and rewriting using AST patterns. Use when user mentions "ast-grep", "sg", or needs to search codebases using Abstract Syntax Tree patterns, find specific code structures, perform complex queries beyond text search, or rewrite code at scale. Triggers on requests for pattern matching, code…
github-cli
This skill should be used when working with GitHub CLI (gh) for repository management, pull requests, issues, API access, GitHub Actions, or automation workflows. Provides comprehensive guidance on gh command patterns, security considerations, and best practices.
android-analysis
Expert Android and Java reverse engineering for APK/AAR/JAR decompilation and inspection. Use when user mentions "decompile", "jadx", "apktool", "reverse engineer", or needs to analyze Android binaries, unpack libraries, understand obfuscated apps, or extract resources from compiled artifacts.