Score7.9
Popularity0.0
Risklow
TierSilver
Score breakdown
Usefulness8.0
Novelty8.0
Momentum7.0
Maturity5.7
Open-source/build8.4
Evidence7.2
Workflow potential9.0
Setup ease6.4
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Most AI agent developers today who need an autonomous agent run a long-lived process (a Python script that polls a queue + a Node.js script that watches a directory + a Go binary that processes events), write custom permission gates, write custom state machines, write custom prompt templates, and rebuild the agent from scratch on every new project. aaronjmars/aeon inverts that pattern: a single MI
Who should use it
AI agent developers, GitHub Actions users, Claude Code / Grok users, autonomous-agent users, MCP-server developers, scheduling/automation users, AI-curious readers tracking the autonomous-agent-framework space, engineering teams wiring autonomous agents to their GitHub Actions + repos, and any developer wiring a fork-and-configure autonomous agent framework + one-shot skill runs + memory + STRATEGY + soul to their AI agent workflow -- and who can pair aaronjmars/aeon with the `git clone` for the clone surface, the `aeon setup` for the setup surface, the `aeon.yml` for the config surface, the `STRATEGY.md` for the north-star surface, the `AGENTS.md` for the agent-instructions surface, the `CLAUDE.md` for the Claude-instructions surface, the `MEMORY.md` for the high-level-memory surface, the `memory/topics/` for the topic-memory surface, the `memory/logs/` for the daily-log surface, the `memory/issues/` for the issue-tracker surface, the `memory/skill-health/` for the per-run-quality surface, the `skills/skill-health/` for the health-skill surface, the `skills/skill-repair/` for the repair-skill surface, the `skills/X/SKILL.md` for the per-skill surface, the `apps/mcp-server` for the mcp-server-entry surface, the `apps/webhook` for the webhook-entry surface, the `apps/dashboard` for the dashboard-entry surface, the `bin/` for the bin surface, the `catalog/` for the catalog surface, the `docs/` for the docs surface, the `output/` for the output surface, the `scripts/` for the build-scripts surface, the `soul/SOUL.md` for the identity surface, the `soul/STYLE.md` for the style surface, the `soul/examples/` for the examples surface, the `soul/data/` for the data surface, the `.github/` for the GitHub-config surface, the `aeon` binary for the binary surface, the GitHub Actions for the GitHub-Actions runtime, the Claude Code for the Claude-Code runtime, the Grok harness for the Grok runtime, the `chain-runner.yml` for the chain-runner surface, the read-only mode for the read-only surface, the write mode for the write-mode surface, the `.mcp.json` for the mcp-config surface, the `scripts/prefetch-*.sh` for the prefetch-script surface, the `scripts/postprocess-*.sh` for the postprocess-script surface, the `./notify` for the notify surface, the `./notify-jsonrender` for the jsonrender surface, the self-healing loop for the self-healing surface, the `docs/CORE.md` for the core-doc surface, the `INDEX.md` for the index surface, and a target skill (e.g. a scheduled research + write + report skill) for the eval surfaceAI agent developers + GitHub Actions users that want the GitHub Actions native (each run is a fresh, headless Claude Code / Grok invocation; no long-lived process) -- the right serverless-ergonomics primitive for any AI agent developer who has been running a long-lived agentAI agent developers + autonomous-agent users that want the one-shot skill runs (a schedule or a manual Run now fires a single skill) + the skill frontmatter (read-only / write + network policy + scripts/prefetch-*.sh) -- the right capability-mode primitive for any AI agent developer who has been writing custom permission gatesAI agent developers + memory users that want the memory/ (MEMORY.md + topics/ + logs/ + issues/ + skill-health/) -- the right memory-ergonomics primitive for any AI agent developer who has been writing custom state machinesAI agent developers + voice / style users that want the STRATEGY.md + the soul/ (SOUL.md + STYLE.md + examples/ + data/) -- the right north-star + voice-ergonomics primitive for any AI agent developer who has been writing custom prompt templatesAI agent developers + engineering teams that want the apps/ (mcp-server + webhook + dashboard) + the chain-runner.yml + the self-healing loop (health skill + repair skills) + the 4-field corroboration (forks 205, size 35956KB, subscribers 5, pushed 2026-07-08) + MIT -- the right entry-point-agnostic + transparency primitive for any AI agent developer who has been locked to a single entry point
Who should skip it
Move on from Aeon: Fork-and-Configure Autonomous Agent Framework on GitHub Actions if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
Aeon: Fork-and-Configure Autonomous Agent Framework on GitHub Actions is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-08 and last updated on 2026-07-08. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Aeon: Fork-and-Configure Autonomous Agent Framework on GitHub Actions leads on workflow potential (9.0) and open-source/build quality (8.4); its lowest signal is maturity (5.7), so factor that in before investing setup time. 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 Aeon: Fork-and-Configure Autonomous Agent Framework on GitHub Actions a composite score of 7.9 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 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.
Risk explanation
The 571* / 205-fork / 5-subscriber / 35956KB repo is at active maintenance (pushed 2026-07-08) but the project is a fork-and-configure framework -- the consumer's repo becomes a long-lived skill catalog; the consumer SHOULD review the docs/ + the AGENTS.md + the CLAUDE.md + the STRATEGY.md + the soul/ before forking; the consumer SHOULD pin the Aeon version and review the changelog; the consumer SHOULD note the framework requires GitHub Actions (the consumer's repo must be on GitHub for the agent to run).
Evidence links
Closest alternatives / related signals
open-sourcemitaeon-incaaronjmarsaeonautonomous-agentfork-and-configuregithub-actions
