Argus Project Inventory

IPurpose

Create a shallow, safe inventory of projects so Argus can learn patterns without context bloat or secret exposure.

IIWorkflow

1. Confirm the parent folder to scan.
2. Run the inventory script before opening project files manually.
3. Review only safe metadata: filenames, folder indicators, package manifests, README/AGENTS headings, and validation command hints.
4. Classify each project and recommend the next Argus workflow.
5. Flag projects without .git as source-control risks unless the operator marks them disposable.
6. Capture repeated project patterns as skill opportunities.

IIIScript

Run:

python "C:\Argus Command Center v5_Plugin\plugin\scripts\inventory_projects.py" "C:\Path\To\Projects"

Useful options:

python "C:\Argus Command Center v5_Plugin\plugin\scripts\inventory_projects.py" "C:\Path\To\Projects" --max-depth 2 --output inventory.md
python "C:\Argus Command Center v5_Plugin\plugin\scripts\inventory_projects.py" "C:\Path\To\Projects" --format json --output inventory.json

IVSafety Rules

• Do not read .env, secret, key, certificate, token, credential, database, or binary content.
• Do not inspect dependency folders such as node_modules, .venv, or vendor caches.
• Do not deep-read source files during inventory.
• Do not create skills during inventory; propose skill opportunities for later approval.
• Do not initialize Git during inventory; inventory only reports the recommendation.

VOutputs

Return:

• projects found
• detected project types
• safe metadata indicators
• validation command candidates
• source-control notes
• recommended Argus workflow per project
• repeated skill opportunities
• confidence and remaining risks