Put five recently high-star AI tools from GitHub on one table and a fact that is easy to miss surfaces: their star counts sit side by side, yet the preconditions for starting each barely overlap. One wants Node 24 and Git on the host. One wants an Android phone on 11 or later, and 12 or later before it will operate your apps. One wants a USB cable, adb and jadx. One is satisfied when you copy a folder into a skills directory. One still labels itself early alpha and admits in its README that parts have been built but not yet run live. Star counts alone will not answer the practical question: once you have the repository, what has to be in place before it starts?
Be clear about the boundary first. This piece is not a tool-selection recommendation, not a license comparison, and not a benchmark ranking. It is a checkable, objective comparison of five recently high-star tools at one capture point, November 7, 2026: language, license field, star count, creation date, last push, supported platforms and runtime prerequisites. An earlier open-weight license comparison from October 23, 2026 already works through license terms, so this one does not compare clauses. The AI drama tools comparison from November 2, 2026 and the image editing tools comparison from October 29, 2026 handle creative-tool selection and output quality, so this one does not judge results. The open-source column in the same batch digs into the craft-anything workflow and its alpha boundary; here it is one row in the table. The hotspot column covers the event and official capabilities, and the API setup SOP walks through a five-step API integration and cost math. Those three angles do not substitute for the comparison here.
The verifiable parameter table
Every number below comes from a single GitHub API scrape on November 7, 2026, and each star count carries that capture point. Creation dates and last pushes come from the created_at and pushed_at fields, resolved to the minute. Language and license values are copied from the API together with each README and LICENSE file, without a second layer of interpretation. Nothing here is a score, a rating, or a ranking signal.
| Repository | Language | License | Stars (scraped November 7, 2026) | Created | Last push |
|---|---|---|---|---|---|
| storytold/craft-anything | Rust | README: MIT OR Apache-2.0, at your option; GitHub license field Apache-2.0 | 19,207 | 2026-10-31 | 2026-11-07 10:14 |
heydamir/unslop | JavaScript | CC-BY-4.0 | 11,023 | 2026-10-29 | 2026-11-01 16:46 |
wangzan101/Mika | Kotlin | Apache-2.0 | 7,489 | 2026-10-29 | 2026-11-07 10:00 |
KKKKhazix/agent-autoloop | TypeScript | MIT | 3,841 | 2026-11-03 | 2026-11-07 08:08 |
Verlintas/NOIR | Kotlin | MIT | 2,832 | 2026-10-31 | 2026-11-07 10:26 |
The five rows are listed in the order returned, purely for reading convenience; the order implies no judgment about higher or lower, earlier or later, or any merit at all. No tool gets a score, no positions are assigned, no third-party review numbers are quoted, and no cross-list comparison is made. Each project takes one row here and one section below.
Query the GitHub API directly to reproduce a row; the command below prints the key fields:
gh api repos/storytold/craft-anything --jq '.stargazers_count, .created_at, .pushed_at, .license.spdx_id'Swap the repository path for the other four; created_at and pushed_at are UTC timestamps, so convert to your local zone, and the LICENSE text is the authority where the README and the API field disagree.
Reading the columns: language, license fields and creation dates
Language first. The five repositories span Rust, JavaScript, Kotlin and TypeScript. Kotlin appears twice, for Mika and NOIR; Rust, JavaScript and TypeScript appear once each, for craft-anything, unslop and agent-autoloop. This is the API language field, not a statement about quality, and nothing here infers which language suits which task.
License fields. MIT appears on agent-autoloop and NOIR, Apache-2.0 on Mika, and craft-anything's GitHub license field is Apache-2.0 too, although its README separately states a dual license, "MIT OR Apache-2.0, at your option"; both readings are kept in the table. CC-BY-4.0 appears only on unslop, whose README License section uses it as a content license requiring attribution and a link back to the repository: a content license rather than a software license. That is a note on nature, not a clause comparison and not legal advice; clause work belongs to the October 23, 2026 article, and the LICENSE text remains the authority.
Creation dates fall between October 29, 2026 and November 3, 2026: unslop and Mika on October 29, 2026, craft-anything and NOIR on October 31, 2026, agent-autoloop on November 3, 2026. They were not all published on one day, and this is not a November 7, 2026 launch. Last pushes run from November 1, 2026 to November 7, 2026: unslop stops at 2026-11-01 16:46, the other four land on the morning of November 7, 2026. All are snapshot values, so every number only means something tied to its capture point.
craft-anything: pure Rust, five platforms and the early alpha boundary
Per its README, craft-anything is 100% Rust across macOS, Windows, Linux, FreeBSD and the Web, with three entry points: a desktop app on egui, a CLI and an MCP server. Model backends can point at Anthropic, OpenAI, OpenRouter, xAI or local models, and it can reuse an installed GitHub Copilot, a grok binary over ACP, and Ghidra. The project labels itself early alpha; its README Status section says "building with API keys and other coding agents" is "built, not yet run live", quoted as written rather than expanded into a readiness claim. Installing dependencies runs code, so builder commands execute on your machine and the tool asks before any command type it has not seen in that project. The repository is storytold/craft-anything at https://github.com/storytold/craft-anything . This piece treats it as one row; the workflow and alpha boundary belong to the open-source column.
unslop: a Claude Code and Codex skill and its Playwright prerequisite
unslop is a skill for Claude Code and Codex. Install means copying skills/unslop into .claude/skills/ for Claude Code, or ~/.agents/skills/ for Codex; for one project use that project's .claude/skills/ or .agents/skills/ instead. It is invoked as /unslop or $unslop. Snapshotting a live site or making a story video needs Playwright and its Chromium browser installed from the directory where you run the skill; story videos additionally need ffmpeg on your PATH. The license field CC-BY-4.0 is, per the note above, a content license rather than a software license. These are install and dependency prerequisites only; how well it redesigns an interface is a creative-tool question.
Mika: an on-device Android agent and its version floor
Mika is an on-device Android agent, and its README states there is no Mika server. Model access has two paths: bring your own model API key, or sign in with a ChatGPT, xAI or OpenRouter account. The README says API keys and memories are stored encrypted on the phone, conversations and run records stay on the device, and update checks contact GitHub only. Installation is an APK from Releases. Version tiers: Android 11 or later covers chat, web and files; operating phone apps needs Android 12 or later, with Android 14 or later recommended. This lists the floor only, without enumerating specific apps or inferring abilities the README does not state.
agent-autoloop: Node 24 and a background hub for command-line agents
agent-autoloop lets a command-line agent take jobs in the background and ask a human only when something is uncertain. Platforms are Windows, macOS and Linux. Prerequisites: Node 24 or newer, Git, and one command-line agent already signed in; macOS and Linux additionally need curl, and no GitHub account is required. Cards for decisions can go to a desktop notification, Feishu, DingTalk, WeCom, Slack or Discord. agent-autoloop status shows progress, answer submits a decision, check validates rules. Performance figures in its README are not quoted here and not recast into any benchmark conclusion.
NOIR: adb and jadx on a desktop host
NOIR is an Android privacy audit that runs on a computer. It uses adb to read the app manifest, permissions and APK network endpoints of a connected device, and can call jadx to decompile a single app. The prerequisite is a macOS, Windows or Linux host plus a connected Android device; it does not modify system partitions and does not need root. The program finds adb and jadx in common locations, and --adb and --jadx point to them when auto-detection fails. Checks cover shared UIDs, exported components, cleartext traffic, backup, debuggable and targetSdk. The README also says the tool itself is offline, with no telemetry, version check or crash reporting, and the only external request happens when adb or jadx is downloaded; that is listed without any claim about protection quality.
Network, accounts and local dependencies, laid out side by side
Placing the five sections side by side answers the opening question. On networking: NOIR says the tool itself is offline and needs no account; Mika has no Mika server, contacts GitHub only for update checks, and routes model calls through your own API key or signed-in account; craft-anything can point at a local or a cloud model service; unslop depends on Claude Code or Codex, and snapshotting a live site adds Playwright and Chromium; agent-autoloop's Feishu, DingTalk, WeCom, Slack and Discord channels depend on the network while desktop notifications do not. On accounts, agent-autoloop needs no GitHub account, Mika can use your own API key or a third-party sign-in, and NOIR needs none. On hosts and devices: Mika needs an Android device at the right tier; NOIR needs a host, a connected Android device and adb, with jadx optional and no root; agent-autoloop needs Node 24, Git and a signed-in agent; unslop needs a skill host plus Playwright, Chromium and ffmpeg for snapshots and story videos; craft-anything needs one of its five platforms and a coding agent. These prerequisites do not overlap, so whether one starts is answered by reading each README, not by star counts, which only describe how many people had starred a repository at the capture point.
FAQ
Q1: What exactly are these star counts, and do they change?
A1: The values 19,207, 11,023, 7,489, 3,841 and 2,832 are stargazers_count fields from a single GitHub API scrape on November 7, 2026, and every star count carries that capture point. This is a bookmark counter, not a download count, not a contributor count, and not a review score. Star counts change as people act on them, so quoting them without the capture point is meaningless. No third-party review score is used here, and no cross-list comparison is made; record your own capture point when you check.
Q2: Are the five license fields the same kind of thing?
A2: Not entirely. MIT and Apache-2.0 are software license fields, on agent-autoloop, NOIR and Mika; craft-anything's GitHub license field is Apache-2.0, while its README states a dual license, "MIT OR Apache-2.0, at your option". unslop's CC-BY-4.0, per the README License section, is a content license rather than a software license, requiring attribution and a link back to the repository. This is a note on nature only, not a clause comparison (that belongs to the October 23, 2026 license article) and not legal advice; the LICENSE text is the authority.
Q3: Do all five need a network connection?
A3: The READMEs state different connection prerequisites. NOIR says the tool itself does not connect to the network, with the only external request when adb or jadx is downloaded; Mika has no Mika server, contacts GitHub only for update checks, and routes model calls through your own API key or signed-in account; craft-anything can point at a local model service or a cloud model service; unslop depends on Claude Code or Codex, and snapshotting a live site adds Playwright and Chromium; agent-autoloop's Feishu, DingTalk, WeCom, Slack and Discord channels depend on the network while desktop notifications do not. These are flat restatements with no judgment attached.
Q4: Where exactly do the runtime requirements bite?
A4: Project by project: agent-autoloop needs Node 24 or newer, Git and one signed-in command-line agent, with curl added on macOS and Linux and no GitHub account; Mika installs an APK from Releases, with Android 11 or later for chat, web and files, Android 12 or later for operating phone apps, and Android 14 or later recommended; NOIR needs a macOS, Windows or Linux host plus a connected Android device, uses adb, optionally calls jadx, does not modify system partitions, does not need root, and accepts --adb and --jadx when auto-detection fails; unslop needs Playwright plus Chromium for snapshots and ffmpeg for story videos; craft-anything is 100% Rust across macOS, Windows, Linux, FreeBSD and the Web.
Q5: How can I reproduce these parameters myself?
A5: Query the GitHub API directly: read stargazers_count, created_at, pushed_at and the license field, then check the license nature against the README and LICENSE text. A reproducible command sits in the parameter-table section above. created_at and pushed_at are UTC timestamps, so convert to your local zone; treat the LICENSE text as the authority; and carry your own capture point, since star counts and push times move.
Related reading