Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for operators and terminal-heavy developers who want to test whether a minimal bash-native agent can cover real troubleshooting or coding workflows on machines that cannot justify a heavier runtime.
Who should use it
Who should skip it
Pass on zhihumomo/bashagt if its scope or audience does not match what your team is building right now.
About this signal
zhihumomo/bashagt is tracked by RepoRadar as a developer tool in the Developer Tool / Terminal section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'worth watch' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, zhihumomo/bashagt is strongest on novelty (9.0) and workflow potential (8.6) and weakest on momentum (5.0) — a profile worth weighing against your own priorities. 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 zhihumomo/bashagt a composite score of 7.8 out of 10, placing it in the Silver 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 1.0 and never affects the composite score or tier. The risk label of 'conditional' 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It is still an agent that can operate through a shell on real hosts, so first evaluation should stay on disposable or scrubbed systems; The project is explicitly preview-stage and centers on one very large shell script, so verify reliability before you depend on it during incidents.