How AgentFind judges an agent

Launch-list scope

For the August 15, 2026 snapshot, we combined eight GitHub searches across Agent topics and agent, agentic, autonomous-agent, multi-agent, and coding-agent terms. We also checked well-known repositories that topic search can miss.

A project was eligible only when its repository represented a runnable product or agent that can complete a meaningful multi-step task. We excluded SDKs, orchestration frameworks, tutorials, awesome lists, prompt or skill collections, memory layers, sandboxes, benchmarks, and projects marked archived.

The 20 eligible projects with the most GitHub stars became the launch catalog. This produces a coding-heavy list because developer agents dominate GitHub popularity; we do not quietly rebalance the ranking by category.

What “worth using” means

Our verdict considers five questions:

1. Can the agent finish a concrete task and produce a useful output?
2. Does its setup cost make sense for the intended user?
3. Are permissions, data exposure, and failure risks visible and manageable?
4. Can claims be traced to a current repository or official source?
5. Is the project maintained and licensed clearly enough for the proposed use?

GitHub stars are a discovery and popularity signal only. They can be influenced by age, publicity, audience, and short-term trends. They are never treated as proof of safety, accuracy, or product-market fit.

Verification and updates

Each profile records its source, Star snapshot, repository push date, detected or documented license, dependencies, likely fit, likely misfit, and review date. We plan a weekly link and maintenance check and a monthly review of licenses, pricing, and project status. Until that routine is operational, the date on each profile is the evidence boundary.

Commercial independence

Natural ranking is not changed by sponsorship, advertising, affiliate commission, or vendor requests. AgentFind currently has no sponsored listings or affiliate links. If that changes, paid content will be labelled directly beside the placement and will not alter the natural ranking.

Corrections

Repository owners and readers can request a correction or removal through the contact page. We prioritize verifiable primary-source evidence over marketing claims.