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 agentmods add skills/funkyoz/funkyoz-plugins/project-analyzernpx skills add FunkyOz/funkyoz-plugins --skill project-analyzergit clone --depth 1 https://github.com/FunkyOz/funkyoz-pluginsWhat 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 | $0.00033 | $0.01087 |
| Opus 5 | $0.00016 | $0.00544 |
| Sonnet 5 | $0.00007 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
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 2d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Analyzer Skill
This skill enables comprehensive analysis of software projects to understand their structure, patterns, and conventions before making changes.
When to Use This Skill
- Starting work on a new task in an existing project
- Creating a task breakdown for a feature
- Understanding project conventions before coding
- Reviewing code for consistency
- Setting up a new project with best practices
Analysis Framework
1. Project Structure Analysis
Directory Layout
- Identify the project type (monorepo, single app, library, etc.)
- Map the directory structure
- Understand the organization pattern (by feature, by layer, etc.)
Key Directories to Look For
src/ # Source code
lib/ # Library code
app/ # Application code
tests/ # Test files
docs/ # Documentation
config/ # Configuration
scripts/ # Build/utility scripts
public/ # Static assets
dist/ # Build output
2. Technology Stack Detection
Package Managers & Dependencies
| File | Technology |
|---|---|
package.json |
Node.js/JavaScript |
composer.json |
PHP |
requirements.txt, pyproject.toml |
Python |
Gemfile |
Ruby |
Cargo.toml |
Rust |
go.mod |
Go |
pom.xml, build.gradle |
Java |
Frameworks
- Check dependencies for framework indicators
- Look for framework-specific config files
- Identify framework version
Build Tools
- Webpack, Vite, esbuild (JavaScript)
- Make, CMake (C/C++)
- Maven, Gradle (Java)
- Cargo (Rust)
3. Code Patterns & Conventions
Coding Style
- Check for
.editorconfig - Look for linter configs (
.eslintrc,.prettierrc,phpcs.xml) - Analyze existing code for patterns:
- Naming conventions (camelCase, snake_case, PascalCase)
- Indentation style
- Quote style
- Semicolon usage
Architecture Patterns
- MVC (Model-View-Controller)
- Clean Architecture / Hexagonal
- Repository Pattern
- Service Layer
- Domain-Driven Design
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.
- 2d ago First seen · 198 lines · 33 tokens per session scan A 9693118cb279
project-analyzer is a skill published in the GitHub repository FunkyOz/funkyoz-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 33 tokens to every session and 1,087 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…