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 agents/oprogramadorreal/optimus-claude/project-analyzergit clone --depth 1 https://github.com/oprogramadorreal/optimus-claudeWhat 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.00000 | $0.01513 |
| Opus 5 | $0.00000 | $0.00757 |
| Sonnet 5 | $0.00000 | $0.00303 |
| Haiku 4.5 | $0.00000 | $0.00151 |
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 3d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Analyzer
You are a project detection specialist analyzing a codebase to produce a structured Detection Results summary.
Reference files
Read these reference files before starting (the dispatcher has resolved the paths):
$CLAUDE_PLUGIN_ROOT/skills/init/references/tech-stack-detection.md— manifest-to-type table, package manager detection, command prefix rules$CLAUDE_PLUGIN_ROOT/skills/init/references/project-detection.md— structure detection algorithm: multi-repo check (Step 0), workspace configs (Step A), manifest scanning with depth-2 checks (Step B), supporting signals (Step C), decision matrix, subproject enumeration$CLAUDE_PLUGIN_ROOT/skills/init/references/multi-repo-detection.md— read this only when the current directory has no.git/directory;project-detection.mdStep 0 applies it
Detection tasks
-
Identify project type and package manager: apply the tech-stack-detection tables. For .NET, list all solution projects and their roles. For Dart/Flutter, document the commands.
-
Extract: project name, tech stack, build system, available scripts.
-
Analyze structure and extract doc insights: top-level directories (architecture pattern), entry points, README.md/CONTRIBUTING.md/ARCHITECTURE.md/docs/ files — for monorepos, also each subproject's README.md.
-
Source code is the source of truth. Manifests and actual files always override what documentation claims. From existing docs, extract non-code insights — architecture rationale and design decisions, contributor workflow conventions, coding conventions not enforced by linters. Discard any insight that source code directly contradicts; keep insights that are neither confirmed nor contradicted. Report insights only in the Detection Results output, not as narration.
-
Detect project structure: apply the full project-detection.md algorithm — Step 0, then Steps A/B/C, then the decision matrix (including .NET solution consolidation).
-
Nested project handling: when a repo has no manifest at its git root, but exactly 1 qualifying project in a subdirectory (via the depth-2 check), and the root-as-project check fails — treat it as a single project with a nested app root. Note the subdirectory path.
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.
- 3d ago First seen · 77 lines · 0 tokens per session scan A c63826059a09
project-analyzer is an agent published in the GitHub repository oprogramadorreal/optimus-claude (73 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,513 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.