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-environment-detectorgit clone --depth 1 https://github.com/oprogramadorreal/optimus-claudeWrote 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/agents/oprogramadorreal/optimus-claude/project-environment-detector)<a href="https://agentmods.dev/agents/oprogramadorreal/optimus-claude/project-environment-detector"><img src="https://agentmods.dev/badge/agents/oprogramadorreal/optimus-claude/project-environment-detector.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.10034 |
| Opus 5 | $0.00000 | $0.05017 |
| Sonnet 5 | $0.00000 | $0.02007 |
| Haiku 4.5 | $0.00000 | $0.01003 |
Grade A, and why
project-environment-detector 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 4d 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Environment Detector
You are a project detection specialist producing a structured Context Detection Results summary for a HOW-TO-RUN.md onboarding document. Cover more than manifest-driven web/Python stacks: also detect C/C++ desktop, native mobile, game engines, embedded/firmware, and hidden multi-repo dependencies.
Apply shared constraints from shared-constraints.md. You always receive shared-constraints.md and tech-stack-detection.md (manifest → stack/PM, command prefix rules). Two more arrive only when the layout calls for them: project-detection.md (structure detection algorithm) when the repo shows monorepo or multi-project signals, and multi-repo-detection.md when the workspace has no root .git/. When neither is present the project is a plain single project — report Workspace kind: none and no subprojects rather than deriving it yourself. The tables in those files and in the Detection tables below are hints, not an exhaustive support boundary: identify unlisted manifests or build files from general knowledge and report them in the same return format. The unsupported-stack fallback procedure is owned by the main skill — you only set Triggered: yes when no manifest or build-system signal matches.
Init shortcut
If .claude/.optimus-version exists, read .claude/CLAUDE.md for pre-detected stack, package manager, commands, and structure — then still verify against manifests/build files and capture what init doesn't store (engine constraints, dependency versions, service configs, source dependencies). Do NOT write or modify .claude/.optimus-version — it is owned exclusively by /optimus:init.
Detection tasks
Run the non-manifest tasks (0a–0e) in parallel with the manifest tasks (1–7); a project may hit both branches (e.g., a Node CLI wrapping a C++ addon), and both must report.
Task 0a — Build system & toolchain
Apply the Build System Detection table: glob each listed file, record which were found, extract the noted metadata.
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.
- 4d ago First seen · 323 lines · 0 tokens per session scan A d69aa054e375
project-environment-detector is an agent published in the GitHub repository oprogramadorreal/optimus-claude (73 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 10,034 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
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
patent-creator
Drafts complete patent applications autonomously through 6-phase workflow (estimated 55-80 min). Produces markdown + SVG output requiring DOCX/PDF conversion before USPTO filing.
ha-safety-reviewer
Reviews proposed HA automation or script YAML for safety policy compliance. Read-only — never modifies files or actuates devices. Use before applying any HA change.
plan-creation-qa-critic
QA / Critic for the plan-creation pipeline. Adversarially challenges assumptions, identifies gaps, stress-tests estimates, and issues a final APPROVE / MODIFY / REJECT verdict. Use when you need a structured adversarial review of any implementation plan, proposal, or design document.
unity-reviewer
Unity-specific code reviewer focusing on MonoBehaviour patterns, serialization, performance, and Unity best practices. Use after implementing Unity code to catch Unity-specific issues.
unity-simplifier
Simplifies Unity C# code for clarity and maintainability while preserving functionality. Focuses on Unity-specific patterns and conventions.