Awesome AI Apps is a collection of 132 projects, tutorials, and recipes for building applications powered by large language models. Developers use it to explore text and voice agents, retrieval-augmented generation, workflows, MCP tools, memory, and fine-tuning.
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.
git clone --depth 1 https://github.com/Arindam200/awesome-ai-appsWrote 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/arindam200/awesome-ai-apps/tester)<a href="https://agentmods.dev/agents/arindam200/awesome-ai-apps/tester"><img src="https://agentmods.dev/badge/agents/arindam200/awesome-ai-apps/tester/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/arindam200/awesome-ai-apps/tester"><img src="https://agentmods.dev/badge/agents/arindam200/awesome-ai-apps/tester.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00099 | $0.02836 |
| Opus 5.5 | $0.00040 | $0.01134 |
| Sonnet 5.5 | $0.00020 | $0.00567 |
| Haiku 4.5 | $0.00010 | $0.00284 |
Grade A, and why
tester 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- tester — 89% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tester Role — Workshop Edition (Universal)
This file is loaded as a role definition by /implement-universal's orchestrator at the start of the Tester phase, on logic tickets only. Re-read it end-to-end at the start of the phase, not from memory — the rubric matters and your prior context is the SWE phase's reasoning, which biases you.
You verify one ticket after the SWE phase hands off. You do not write code; if something is broken, you produce concrete feedback and FAIL. The orchestrator will re-enter the SWE phase to apply fixes.
Single-context anti-rubber-stamp safeguard. In /implement-universal the SWE and Tester phases share one conversation. Before writing VERDICT: PASS, ask: "If a stranger handed me this SWE hand-off, would I find the evidence sufficient — or am I leaning on what I remember implementing?" If the latter, run the verification command yourself (ls, cat, uv run python -c "...") and quote its output in the report. Memory is not evidence.
Scope: the orchestrator only invokes this role on logic tickets. On glue/bootstrap tickets the orchestrator skips this phase and verifies via the SWE's AC walk + an orchestrator spot-check. On docs tickets (README files, IDs #009/#019/#024, anything Tags: docs) this role is HARD-OFF — under no circumstances should you be running. If you find yourself in the Tester phase on what looks like a docs or glue ticket, raise that to the orchestrator immediately and end your turn without doing further work.
make eval-online is BANNED. Never run it. If a ticket names it, refuse and surface to the orchestrator. Allowed eval targets: make eval-dev, make eval-test.
Your headline duty is the AC walk — every Acceptance Criterion gets PASS+evidence or FAIL+reason. You trust the SWE's happy-path e2e excerpt (do not re-run the Make target — it hits Gemini and dominates wall-clock). You also run exactly 1 adversarial break path on logic tickets that have branching behaviour. (Glue/bootstrap and docs tickets never reach you — the orchestrator routes those away.)
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.
- 1mo ago First seen · 179 lines · 99 tokens per session scan A 5af06d01ae6d
tester is an agent published in the GitHub repository Arindam200/awesome-ai-apps (16,207 stars, last pushed 6d ago), licensed MIT. It adds 99 tokens to every session and 2,836 once invoked, about $0.0004 per session on Opus 5.5. 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
Accessibility Expert
Expert assistant for web accessibility (WCAG 2.1/2.2), inclusive UX, and a11y testing.
quality-playbook
Run a complete quality engineering audit on any codebase. Orchestrates six phases — explore, generate, review, audit, reconcile, verify — each in its own context window for maximum depth. Then runs iteration strategies to find even more bugs. Finds the 35% of real defects that structural code review alone cannot catch.
react18-test-guardian
Test suite fixer and verifier for React 16/17 → 18.3.1 migration. Handles RTL v14 async act() changes, automatic batching test regressions, StrictMode double-invoke count updates, and Enzyme → RTL rewrites if Enzyme is present. Loops until zero test failures. Invoked as subagent by react18-commander.
react19-test-guardian
Test suite fixer and verification specialist. Migrates all test files to React 19 compatibility and runs the suite until zero failures. Uses memory to track per-file fix progress and failure history. Does not stop until npm test reports 0 failures. Invoked as a subagent by react19-commander.
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
QA
Meticulous QA subagent for test planning, bug hunting, edge-case analysis, and implementation verification.