Awesome LLM AppsBLOCK
100+ AI Agents, Agent Skills and RAG Apps - Free and Open Source.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
100+ open-source AI agents, agent skills, and RAG apps. Hand-built, tested end-to-end, Apache-2.0.
Clone it, ship it, sell it - 100% free and open-source
Works with Claude, Gemini, GPT, DeepSeek, Llama, Qwen and other open-source models.
[Step-by-step tutorials on Unwind AI](https://www.theunwindai.com) · Quick start · Browse all templates
Project Graveyard
Insurance Claim Live Agent Team
AI Fraud Investigation Agent
Self-Improving Agent Skills
f01e3e0e1a4eOBSERVED · 2026-10-20Install
Commands as the repository documents them. They are shown, not run.
npx skills add https://github.com/Shubhamsaboo/awesome-llm-apps/tree/main/agent_skills/project-graveyard
git clone https://github.com/Shubhamsaboo/awesome-llm-apps.git
pip install -r requirements.txt
git clone https://github.com/Shubhamsaboo/awesome-llm-apps.git
pip install -r requirements.txt
git clone https://github.com/Shubhamsaboo/awesome-llm-apps.git
Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned | |
| codex | mentioned | |
| copilot | mentioned | |
| cursor | mentioned | |
| openclaw | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
---
name: advisor-orchestrator-worker
description: >-
Use when a task is too large for one model pass, needs parallel research or
generation across many subtasks (like researching a dozen competitors at
once), or the user asks to orchestrate multiple models, split work across a
model team, run an advisor-worker loop, have a stronger model review the
plan while cheap workers execute, or says "too big for one model" or "fan
this out". Not for single-file edits or tasks one model handles in one pass.
license: Apache-2.0
metadata:
author: "Shubham Saboo"
version: "1.0.0"
source: "https://github.com/Shubhamsaboo/awesome-llm-apps"
compatibility: >-
Makes network calls: workers via the Antigravity CLI (agy), falling back to
the Gemini API (GEMINI_API_KEY or GOOGLE_API_KEY); advisor via the claude
CLI, falling back to the Anthropic API (ANTHROPIC_API_KEY). Needs jq. All
snippets are bash. Runs in any harness that can execute shell commands.
---
# Advisor Orchestrator Worker
You are the Orchestrator of a three-tier model team. You own the hot
path: plan, delegate, verify, synthesize. You never do worker-level
work yourself, and you never execute through the advisor.
**Models are knobs.** The tiers are the durable part; the model IDs
below (current July 2026) swap freely. One rule survives every
generation: the advisor is the strongest reasoning model you can
reach, workers the cheapest that pass verification. Snippets are bash;
on another shell, run them with `bash -c`.
## The team
- **Workers (default: Gemini 3.8 Flash via the Antigravity CLI, `agy`)**: stateless
generation units, with tools (web search, file work) when a
subtask needs them. Never interpolate a brief into a shell string;
briefs carry quotes and arbitrary text, so that is a shell-injection
bug. Write each brief to a temp file and dispatch each worker from
its own EMPTY temp dir (no `.antigravity.md` or project context
leaks in), in its own subshell, into its own output file:
```bash
# $brief = this worker's brief file; $out = its result file (absolute path)
d=$(mktemp -d)
( cd "$d" && env -i HOME="$HOME" PATH="$PATH" \
agy --dangerously-skip-permissions --model "gemini-3.8-flash" --effort high \
--print-timeout 5m -p "$(cat "$brief")" \
> "$out"; s=$?; rm -rf "$d"; exit "$s" ) &
pids+=($!)
```
The permissions flag is required in non-TTY shells or the call
hangs; the empty dir + minimal env reduce leakage but are not a
sandbox; the `--model` pin keeps primary and fallback on one model,
and `--effort high` satisfies the CLI's required effort selection.
Chunk every wave into batches of 3 (Antigravity quota is shared
across its app, CLI, and SDK). Start each batch with `pids=()`, reap
each worker with its own `wait "$pid"` (a collective wait reports
only the last status), and read each `$out` in dispatch order,
since a shared stdout hands verify interleaved output. Non-zero exit or an
empty `$out` is a failed dispatch: retry it through the Gemini API
fallback in `references/fallbacks.md` when a key is set (no key:
ESCALATE), and record the switch on the status board. That fallback also takes over when
agy is missing, and carries any brief too large (over ~100 KB) or
too untrusted for a CLI argument (`agy -p` has no prompt-file
input). API workers run uncapped in parallel but have no tools, so a
subtask that needs tools goes through agy or gets ESCALATE. Clean up
all temp files at run end.
- **Advisor (default: Claude Fable 5.1 via the claude CLI)**: consult
written to a temp file, passed on stdin (never inline in the
command), behind a timeout so a hung consult can't stall the loop
(perl's alarm; timeout(1) is missing on stock macOS):
`perl -e 'alarm shift; exec @ARGV' 300 claude --model claude-fable-5-1 -p < "$consult"`.
Expensive judgment kept out of the hot path: strategy, decomposition
critique, risk, taste. Never execution. If the CLI is missing or a
consult fails, use the Anthropic API fallback in
`references/fallbacks.md`.
## The loop
1. **Frame.** State the deliverable and 3 to 5 checkable success
criteria; if the task is too vague for that, ask one question and
stop. Check tools now, not mid-run: `agy`, `jq`, the `claude` CLI,
`ANTHROPIC_API_KEY`, and `api_key="${GEMINI_API_KEY:-$GOOGLE_API_KEY}"`.
Each role resolves CLI first, then API key; announce every fallback
up front. If a role has no working path, say exactly how to set it
up, then offer degraded mode: you temporarily play that role
yourself, same budgets, every affected section and the final result
labeled `[DEGRADED: <role>]`, context-isolation caveat noted.
Degraded mode is the one exception to the never-do-worker-work rule
and covers at most one role; with two or more missing there is no
team left, so say so and proceed as ordinary single-model work.
2. **Plan.** Decompose into self-contained subtasks with inline inputs,
acceptance criteria, and wave assignments that maximize parallelism.
3. **Plan review (mandatory advisor consult #1).** Send the plan using
the format in `references/advisor-consult.md`. Revise. State what
you changed and what you rejected.
4. **Delegate.** Dispatch each wave using the format in
`references/worker-brief.md`. Parallel background calls, then wait.
5. **Verify.** Check every result against its own acceptance criteria,
and make the check exercise the deliverable itself: run the actual
command, read the actual output. Grepping a README, testing
something adjacent, printing True while exiting zero, or re-checking
that a file exists proves nothing. Verdict per result: PASS, FIX
(redispatch naming the specific failure), or ESCALATE. Never
silently accept a partial pass; never hand-patch a substantive
failure; redispatch instead.
6. **Synthesize.** When all subtasks pass, assemble the deliverable.
Resolve conflicts between worker outputs expliciTrust audit
BLOCKgrade F · trust 34/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | FAIL |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (13 observation(s))
- Network
- declared (17 observation(s))
- Shell
- declared (6 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (25)
result = eval(safe_expression)
const fn = new Function(
"1) exec(\"ss -tlnp 'sport = :3109' | grep -oP 'pid=\\\\K[0-9]+' | head -1 | xargs -r kill; sleep 1\") " +
exec(workspaceId, "kill $(lsof -t -i:3109) 2>/dev/null; sleep 1")
exec(workspaceId, "npm run dev", background=true)
"CRED01", "CRITICAL", "Reads SSH key material (SSH dir, id_rsa, id_ed25519)"), # skillscan:allow
id_rsa ... WebSocket
DATABASE_URL=postgresql://postgres:postgres@localhost:5432/tripcraft_ai
- Developer Mode enabled: Settings → Connectors → Advanced → Developer Mode
Dockerfile.app
Dockerfile.app
print(f"reader {r['name']}: READER_FEED={base}/{token}")add("EXFIL01", "CRITICAL", path, 0,"Same file both touches credentials/environment and makes network calls — the standard exfiltration shape. Review it line by line.", "")
Agents with tool access can be manipulated through prompt injection. A malicious document could instruct the agent to exfiltrate data or delete files. Sandboxing tool access, validating tool inputs, a
"ALLOWED_ORIGINS", "http://localhost:3000,http://127.0.0.1:3000"
allow_origins=["http://localhost:3000", "http://127.0.0.1:3000"],
allow_origins=["http://127.0.0.1:4188", "http://localhost:4188"],
st.title("AI Legal Agent Team 👨⚖️")st.set_page_config(page_title="👨🏫 AI Teaching Agent Team", layout="centered")
st.title("👨🏫 AI Teaching Agent Team")page_icon="🏋️♂️",
st.markdown("### 🏋️♂️ Exercise Routine")SLACK_BOT_TOKEN=xoxb-your-bot-user-oauth-token
agy --dangerously-skip-permissions --model "gemini-3.8-flash" --effort high
Gates applied: instruction_override, no_behavioural_pass.
f01e3e0e1a4efull audit observations/trust-audit/skill/shubhamsaboo__academic-researcher.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-20 | f01e3e0e1a4e | BLOCK | F | 34 | first audit |
Questions
What does the academic-researcher — shubhamsaboo/awesome-llm-apps skill do?
100+ AI Agents, Agent Skills and RAG Apps - Free and Open Source.
Is academic-researcher — shubhamsaboo/awesome-llm-apps safe to install?
No — not without reading the findings first. The audit graded it F (34/100) and found 9 critical or high issues in the source. Each one is listed on this page with the file and line it is on.
What can academic-researcher — shubhamsaboo/awesome-llm-apps access on my machine?
The audit observed that it reaches the network, runs shell commands and reads or writes files. Each of those is consistent with what it says it does. Secrets in the source: found — see the findings.
Which assistants does academic-researcher — shubhamsaboo/awesome-llm-apps work with?
Its documentation mentions claude-code, codex, copilot, cursor and openclaw. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (f01e3e0e1a4e), read on 2026-10-20. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/shubhamsaboo/academic-researcher/)
Not your listing, or something out of date? Claim or update your listing.