Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who are tired of recreating prompts, hooks, skills, and long-term memory every time they move between coding-agent tools.
Where this stands now
codejunkie99/agentic-stack ranks #31 of 1042 tracked Developer Tools items by composite score (8.4 against a section median of 4.9). The section currently carries 811 Bronze, 127 Silver, 103 Gold, 1 Low Signal. RepoRadar has retained observations for this record since 2026-06-28 (92 days in the current window). Signal extremes versus the section: momentum at the 92th percentile; novelty at the 94th percentile.
Who should use it
Who should skip it
Move on from codejunkie99/agentic-stack if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
codejunkie99/agentic-stack is tracked by RepoRadar as a framework in the Developer Tools section. First seen 2026-06-28; the source record was last checked on 2026-06-28. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for codejunkie99/agentic-stack are workflow potential (9.9) and practical usefulness (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The codejunkie99/agentic-stack record combines a 8.4/10 composite score with separate popularity (3.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
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 installer writes hooks, config, and memory surfaces into multiple local agent environments, so review what it changes before pointing it at a production workspace; Its shared brain and dashboard can aggregate sensitive repo context, so keep secrets and regulated codebases out of early pilots until the data flow is clear; Upgrade commands should be tested with the dry-run path first because the value proposition depends on modifying live agent setups safely.