The Problem
This repository contains 7 self-contained LLM application projects that share no unified architecture, creating discoverability and integration challenges. Teams evaluating the stack must assess each project independently rather than understanding a coherent system. The collection spans autonomous game players, multi-agent teams, RAG tutorials, and voice agents—valuable individually but opaque as a portfolio.
What This Does
The repository organizes 1073 files across 7 distinct projects: advanced_ai_agents (462 files, 308 code files), ai_agent_framework_crash_course (250 files, 112 code files), advanced_llm_apps (174 files, 37 code files), rag_tutorials (72 files, 25 code files), starter_ai_agents (51 files, 20 code files), voice_ai_agents (12 files, 6 code files), and mcp_ai_agents (17 files, 5 code files). Recurring techniques include RAG implementations (rag_tutorials/ai_blog_search/app.py, rag_tutorials/rag_chain/app.py), multi-agent team patterns (advanced_ai_agents/multi_agent_apps/agent_teams/ with 8 agent team variants), and autonomous agents for chess, tic-tac-toe, and 3D pygame. Entry points such as advanced_ai_agents/autonomous_game_playing_agent_apps/ai_tic_tac_toe_agent/app.py:34 reach 309 functions, while rag_tutorials/ai_blog_search/app.py:153 (agent) reaches 44 functions with no internal callers. The code touches 27 model inference calls, 41 filesystem operations, 76 database operations, and 27 outbound network calls across resolved edges.
How It Is Wired
Execution starts at individual entry points rather than a single root. The most connected module is advanced_ai_agents/multi_agent_apps/ai_news_and_podcast_agents/web/src/services/api (Ca 22, Ce 0, instability 0)—22 modules depend on it with high blast radius. The internal call graph has 1216 resolved call edges; execute_query is called from 95 places, Agent from 43, get_session from 26. Representative edges: main -> Agent x18, initialize_agents -> Agent x14, generate_travel_plan -> update_trip_plan_status x11. Five files carry the highest cognitive-load findings: Sidebar.js, ActivePodcastPreview.js, AudioConfirmation.js all have max indentation depth 10, making control flow hard to follow. Duplicated code blocks appear across 184 files with 3314 repeated 6-line patterns in legal and real estate agent teams—extract shared helpers to DRY the repeated logic. Two critical security findings exist: h11@0.14.0 CVE-2025-43859, gitpython@3.1.44 CVE-2026-42284, and ANTHROPIC_API_KEY committed in .github/workflows/claude.yml where contributor-controlled input reaches a job with publish tokens.
How To Use It
Setup: This is a collection of 7 projects with no single install command. Each project has its own requirements.txt. For example, advanced_ai_agents/autonomous_game_playing_agent_apps/ai_tic_tac_toe_agent/requirements.txt and advanced_ai_agents/multi_agent_apps/agent_teams/ai_travel_planner_agent_team/backend/requirements.txt. Clone with: git clone https://github.com/moses-y/awesome-llm-apps
Configuration: Environment variables are project-specific. The travel planner team uses .env.example at advanced_ai_agents/multi_agent_apps/agent_teams/ai_travel_planner_agent_team/backend/.env.example. The legal agent team has similar examples. No single .env or config file spans all projects.
Running it: Choose a project directory and invoke its entry point. To run the tic-tac-toe agent: python advanced_ai_agents/autonomous_game_playing_agent_apps/ai_tic_tac_toe_agent/app.py. For the RAG blog search: python rag_tutorials/ai_blog_search/app.py. Each project's README documents its specific startup command.
Real-World Use
A developer wants to evaluate multi-agent team patterns for a customer support system. They examine advanced_ai_agents/multi_agent_apps/agent_teams/ai_financial_coach_agent/ai_financial_coach_agent.py (13 functions, 13 classes, called from 1 other file) to understand agent role definitions, then look at advanced_ai_agents/multi_agent_apps/agent_teams/ai_legal_agent_team/legal_agent_team.py for team orchestration patterns. The ai_travel_planner_agent_team/backend/services/db_service.py (4 functions, called from 21 files) shows database service patterns with initialize_db_pool, close_db_pool, get_db_session, execute_query that could be adapted. The rag_tutorials/rag_chain/app.py:81 run_rag_chain reach 44 functions and demonstrates retrieval-augmented generation workflows.
Code Health & Issues
The static analysis found 189 total findings: 70 high, 119 medium, 0 low across 3 kinds. Specific findings:
[MEDIUM/clarity] Hub module:advanced_ai_agents/multi_agent_apps/ai_news_and_podcast_agents/web/src/services/api.js— 22 modules depend on this one; high-blast-radius churn. Keep stable and small; move volatile logic out.[HIGH/cognitive_load] Deep nesting x58:advanced_ai_agents/multi_agent_apps/ai_news_and_podcast_agents/web/src/components/Sidebar.js,ActivePodcastPreview.js,AudioConfirmation.js— max indentation depth 10. Flatten with early returns/guard clauses; extract inner blocks.[HIGH/clarity] Duplicated code blocks:advanced_ai_agents/multi_agent_apps/agent_teams/ai_legal_agent_team/legal_agent_team.py,local_ai_legal_agent_team/local_legal_agent.py, and real estate team variants — 3314 repeated 6-line blocks across 184 files. Extract shared helpers; DRY the repeated logic.
Code health audit (14 findings, 2 critical, 4 high, 6 medium, 2 low):
[CRITICAL] Upgrade the pinned dependency carrying a critical advisory:h11@0.14.0CVE-2025-43859,gitpython@3.1.44CVE-2026-42284,pyarrow@19.0.1CVE-2026-25087. Fix: upgrade to fixed versions and commit lockfile.[CRITICAL] Keep secrets out of workflows a fork can trigger:.github/workflows/claude.ymlcontainsANTHROPIC_API_KEY. Fix: move secret-using steps intoworkflow_runjob that never checks out pull request code.[HIGH] Pin third-party GitHub Actions to a commit SHA:anthropics/claude-code-action@betain.github/workflows. Fix: replace@vNwith 40-character commit SHA.[HIGH] Upgrade the pinned dependency carrying a published advisory:protobuf@5.29.3CVE-2026-0994,pyasn1@0.6.1CVE-2026-23490,python-multipart@0.0.20CVE-2026-53539,requests@2.32.3CVE-2024-47081, and 10 more. Fix: upgrade and commit lockfile.[HIGH] Commit a lockfile beside the manifest:advanced_ai_agents/multi_agent_apps/ai_news_and_podcast_agents/web/package.jsonhas no lockfile. Fix: run package manager once and commit generated lockfile.[HIGH] Make CI invoke the test suite it has: 11 test files, no test command in any workflow. Fix: add test step to existing workflow.[MEDIUM] Enable Dependabot or Renovate: 143 manifests, no update bot configured. Fix: commit.github/dependabot.ymlcovering repo ecosystems plus github-actions.[MEDIUM] Pin the container base image by digest:advanced_ai_agents/multi_agent_apps/agent_teams/ai_travel_planner_agent_team/backend/Dockerfileusespython:3.12-slim-bookworm(mutable). Fix: usepython:3.12-slim-bookworm@sha256:<digest>and enable Dependabot docker ecosystem.
Beyond the measured findings: committed secrets in .github/workflows/claude.yml, 2 blobs over 5MB (streaming-ai-chatbot.gif 23.8MB, github thinkpath video.mp4 19.1MB) not on LFS, and no dependency vulnerability scanning in CI.
The Bottom Line
This repository is a valuable portfolio of 7 independently viable LLM application projects—game-playing agents, multi-agent teams, RAG systems, and voice interfaces—that demonstrate practical patterns across OpenAI, Anthropic, Gemini, and open-source models. However, the absence of a unified architecture, critical dependency vulnerabilities in pinned packages, secrets in workflows, and missing lockfiles mean it should be evaluated project-by-project rather than as an integrated system. Teams should clone the specific projects relevant to their needs, upgrade the called-out dependencies, and remove the committed API key before running any CI or sharing code.