Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Most autonomous-agent frameworks today have shipped enormous codebases -- tens of thousands of lines, large dependency trees, dozens of pre-loaded skills, complex tool-bridge interfaces -- that are hard to audit and harder to extend. lsdefine/genericagent inverts that pattern: the canonical MIT open-source minimal-seed self-evolving autonomous agent framework where the entire starting point is jus
Who should use it
Who should skip it
Skip lsdefine/genericagent if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
lsdefine/genericagent is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-09 and last updated on 2026-07-09. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for lsdefine/genericagent are workflow potential (9.2) and momentum (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned lsdefine/genericagent a composite score of 8.5 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 0.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The 13; 341* repo is at production-grade maturity but the consumer SHOULD note the project's self-evolving Skill model means Skills accumulate over time -- review the Skills marketplace security model before adopting in shared / multi-tenant environments; the consumer SHOULD review the system-level access scope for the 9 atomic tools (browser / terminal / filesystem / keyboard / mouse / screen vision / mobile / shell / task) -- these tools grant broad host control by design; the consumer SHOULD review the LLM credential storage model.