P01
The Contrarian
Tier A
/u/MAGIC_EYE_BOT
While every other entrant ports the obvious AI-buzzword bot (RepostSleuth, BotDefense clones), the unfashionable truth is that MAGIC_EYE_BOT is the bot mods of large image subs actually still configur
"Everyone's porting the trendy bot. We're porting the one r/pics mods actually still edit the wiki for — MAGIC_EYE_BOT, terminal-style, parity-proven, sub-second on Devvit."
Surface: terminal-style mod console embedded in the subreddit's Mod Tools tab — keyboard-first 'config diff' viewer that shows the legacy wiki YAML o
RepostSleuthBot
Port RepostSleuthBot to Devvit so the moderator-author can finally turn off the always-on Postgres/Redis box, kill the cron-driven token rotation, and let Devvit's managed runtime + media trigger abso
"RepostSleuthBot, ported to Devvit — same rules, sub-second triggers, zero hosting bill, and an ops dashboard that proves the time saved instead of promising it."
Surface: Operator status board: a Devvit subreddit-app settings page that doubles as a live ops dashboard — uptime %, p50/p95 trigger latency, hash-l
P03
The Speed-Obsessed
Tier A
u/RemindMeBot
RemindMeBot is the perfect speed-port: a single comment-summon trigger plus a delayed-callback delivery. Strip Watchful1's 7-year PRAW + sqlalchemy codebase to ONE Devvit trigger + ONE Scheduler job a
"RemindMeBot, ported to Devvit in 4 days: one trigger, one scheduler, zero servers — Watchful1's 1.5M reminders survive Data API deprecation with the smallest diff possible."
Surface: Single Devvit install card with a 4-day countdown CTA, one-click 'Install on r/test', and an auto-firing demo reminder in 60 seconds. Onboar
P04
The Cost-Conscious
Tier B
ContextMod
⚠ 3-year dormant runtime; codebase intact
ContextMod's value is the rules YAML — its cost is the infra. Port the rules engine and YAML config loader to Devvit so every operator's $30+/mo VPS bill collapses to $0, while the parity surface (pos
"ContextMod's $47/mo hosting bill ported to Devvit's free runtime — same rules.yaml, zero VPS, zero token rotation, $564/year saved per operator."
Surface: Devvit app (free Reddit-hosted runtime) + Redis-backed key-value (Devvit free tier) for rule cache + YAML rules pasted into Devvit settings
P05
The Design-Forward
Tier A
RepostSleuthBot
Repost detection isn't a data problem — it's a perception problem. Mods need to see the duplicate to trust the verdict, not parse a wall of similarity percentages buried in a comment thread. Devvit le
"RepostSleuth, reborn as a visual verdict card — mods see the duplicate, read the rationale, and action it in one tap, without ever leaving the post."
Surface: First screen IS the pitch: a Devvit custom post that renders the flagged submission and the top-3 historical matches side-by-side as a polis
AssistantBOT
⚠ 5-year dormant; permission-path uncertain
Mods don't want one-off dashboards — they want a sortable, filterable grid of every modlog event, every removed post, every takedown reason, with CSV export. Port AssistantBOT's stats engine into Devv
"AssistantBOT, but the weekly stats comment is now a sortable Devvit grid: 8 columns, filter chips, CSV export, keyboard-driven — mods triage in rows, not tabs."
Surface: Devvit custom-post 'ModSheet' — sticky-header data grid with sortable columns (timestamp, author, action, rule, latency_ms, queue_depth), mu
P07
The Mobile-First
Tier A
/u/MAGIC_EYE_BOT
Image-sub mods triage 80% of repost reports from a phone — in line, on transit, between meetings — but Reddit's official mobile mod tools force pinch-zoom on tiny side-by-side thumbnails. The Devvit p
"Tinder-for-reposts: MAGIC_EYE_BOT's pHash queue, swipeable from the phone where mods actually live."
Surface: Devvit custom post rendered as a phone-frame swipe deck — single-column, 48px minimum tap targets, status-bar safe area, bottom sheet for th
P08
The Slack-Native
Tier A-
u/AlertBot (Alert-Bot-Reddit)
AlertBot's legacy delivery surface (private DMs blasted at one subscribed user) is the exact wrong shape for moderator team workflows — alerts vanish into a single mod's personal inbox with zero team
"AlertBot reborn — keyword alerts arrive as modmail threads, mod teams reply with slash commands, Opus 4.7 parses intent. Chat is where moderation happens."
Surface: primary_surface = Devvit ModMail conversation (the chat-thread surface) for both alert delivery AND command reply. Slash-style commands (`!a
P09
The CLI Devotee
Tier B
ContextMod
⚠ 3-year dormant runtime; codebase intact
ContextMod's superpower was always the rule file — moderators who could write a JSON ruleset shipped policy in minutes, but the GUI ports always lost that keystroke velocity. Port ContextMod to Devvit
"ContextMod, ported to Devvit, but you never leave the keyboard — vim-modal rule editing, `:dry-run` REPL, and Opus-powered `:explain` right inside the modqueue."
Surface: Devvit custom post + settings page rendered as a terminal emulator (monospace, OKLCH phosphor palette, blinking caret). Web UI appears once
ContextMod
⚠ 3-year dormant runtime; codebase intact
Port v1 of ContextMod isn't just a bot migration — it's the seed of a Community-AI Compact: a future where every subreddit has a native, mod-authored AI conscience that learns the sub's values from re
"ContextMod v1 ports the rules; v5 becomes your subreddit's AI conscience — a mod-authored, mod-accountable assistant that learns your community's values and explains every call."
Surface: Devvit-native modqueue overlay with a single 'Why?' glyph per item that opens a glass-morphism context card — natural-language reasoning, le
P11
The Pragmatist
Tier A
Flair_Helper2
Don't reinvent. Port the smallest mod bot with the cleanest spec. Flair_Helper2 is one trigger (PostFlairUpdate), one config file (wiki YAML), and ~6 actions. That fits 4 days with margin to spare and
"Flair_Helper2 reborn on Devvit — same YAML, same flairs, same actions, zero hosting. Ships day 4, works on day 5."
Surface: Devvit Web app (TypeScript) + Postgres-equivalent via Devvit Redis KV. Stack: Devvit 0.11 stable (not preview), TS 5.4, Zod for YAML validat
P12
The Privacy Hawk
Tier B
ContextMod
⚠ 3-year dormant runtime; codebase intact
ContextMod's whole job is reading sensitive cross-subreddit user histories — exactly the data class that the legacy 'self-hosted server + broad OAuth' model leaks worst. Porting to Devvit isn't just '
"ContextMod, ported to Devvit so user histories stop leaving Reddit — same rules, two OAuth scopes instead of seven, hashed storage, auto-expiring, with a privacy receipt every mod can show their community."
Surface: Devvit-sandboxed rule engine (PostSubmit / CommentSubmit / ModAction triggers) with local-first evaluation in Devvit Redis (per-install, per
P13
The Data Nerd
Tier B-
AssistantBOT
⚠ 5-year dormant; permission-path uncertain
Re-platform AssistantBOT (Artemis) onto Devvit so its statistics engine — submission cadence, flair distribution, top contributors, traffic deltas, mod-action breakdowns — runs as a native Reddit dash
"AssistantBOT, ported to Devvit as a live mod dashboard — the stats your sub already trusted, now charted inside Reddit with a measurable time-savings delta on the front page."
Surface: Devvit custom-post dashboard pinned to the sub: KPI strip (WAU, submit rate, removal rate, mod-action p50 latency) + 30/90-day sparklines +
Flair_Helper
⚠ Original abandoned; pivot to Flair_Helper2 likely
The original Flair_Helper already taught users why their post was removed via canned rule citations. Devvit lets us turn that one-shot removal comment into an in-thread learning moment: the OP sees an
"Flair_Helper, ported to Devvit and turned into a teacher: every removal becomes an inline lesson on the OP's post, so users learn the rules instead of rage-quitting modmail."
Surface: Devvit post-level custom post + modqueue overlay. Onboarding-rich: every removal generates an inline 'Why was this removed?' card on the OP'
u/RemindMeBot
RemindMeBot은 1인 알림 도구가 아니라 1.5M+ 활성 리마인더가 흐르는 거대한 멀티유저 그래프다. 모든 리마인더는 요청자(requestor) + 소환자(u/RemindMeBot) + N명의 'me too' bystander로 구성된 다인 스레드이며, Devvit 포팅의 핵심은 이 piggyback을 라이브 카운터·그래프·모드 핀 surface로
"RemindMeBot을 1인 타이머에서 다인 커뮤니티 모먼트 그래프로. 1.5M 리마인더가 만드는 네트워크를 모드가 직접 큐레이션하는 Devvit 포트."
Surface: Devvit single-workspace = 한 reminder thread가 곧 다인 워크스페이스. role-based: requestor / summoner(bot) / bystanders / mod-curator. inline @mention
P16
The Solo Founder
Tier A
Flair_Helper2
A single human keeps Flair_Helper2 alive on a personal VPS — token rotations, OAuth re-auths, modlog poller crashes at 3am all land on one pager. Port it to Devvit and the bot lives inside Reddit's ru
"Flair_Helper2, ported to Devvit — same flair-driven mod actions, zero VPS, zero pager. Give the solo maintainer their weekend back."
Surface: Devvit app with a single owner-admin panel (no role/permission matrix — installer = admin = user). One YAML-equivalent rules editor, one liv
P17
The Enterprise Buyer
Tier B
ContextMod
⚠ 3-year dormant runtime; codebase intact
Reframe the port as a compliance-grade migration: every rule the legacy ContextMod instance ran becomes an auditable Devvit policy with signed change history, role-scoped overrides, and an SLA gauge —
"ContextMod, re-shipped as a SOC2-vibe Devvit control plane: every removal signed, every rule role-scoped, every latency SLA-tracked — so head-mods of 500K+ subs can sign off on the migration."
Surface: Devvit modtools panel rendered as an enterprise control center: (a) immutable Audit Log table (actor, rule_id, target, decision, hash, times
AssistantBOT
⚠ 5-year dormant; permission-path uncertain
AssistantBOT was the friendly archivist of moderation — it sent mods a tidy weekly newsletter and quietly enforced flair. The port isn't a feature list; it's a brand revival. We re-launch it on Devvit
"AssistantBOT, redrawn for Devvit — same beloved weekly digest and flair enforcement, now wearing a wordmark, a gradient, and a voice mods will actually pin."
Surface: Devvit-native install, but the discovery surface is a scroll-driven brand storyscape: hero with the new AssistantBOT mark, a parallax 'befor
/u/MAGIC_EYE_BOT
MAGIC_EYE_BOT's value is invisible — mods only notice fewer reposts in modqueue. Ship it not as an app but as a headless Devvit SDK that other Devvit apps compose: three lines of code, zero new UI, re
"Repost detection as a three-line import. MAGIC_EYE_BOT ported headless — no UI, no app, just a Devvit SDK your existing mod app calls."
Surface: npm package `@magic-eye/devvit` — drop-in import, settings.json-driven config, programmatic `MagicEyeRepostCheck.run(post, ctx)` call inside
P20
The OSS Maintainer
Tier B
ContextMod
⚠ 3-year dormant runtime; codebase intact
Reddit's Data API sunset is about to orphan ContextMod and the dozens of mod teams who built rule-sets on top of it. We rescue the bot by porting it to Devvit AND handing the keys to a neutral OSS org
"ContextMod survives the Data API sunset as a community-owned Devvit app — same YAML rules, same behavior, new runtime, governed by the mods who depend on it."
Surface: GitHub repo README is the product. Devvit install is the reference implementation. Issues + Discussions + RFC PRs are how mods adopt and ste
P21
The Indie Hacker
Tier A
RepostSleuthBot
Treat the hackathon as a customer-acquisition channel: pick the ONE bot every mod already begs for so the Devvit port hits maximum install velocity post-prize, converting Developer Funds engagement-mi
"RepostSleuth, ported to Devvit — every mod's most-requested bot becomes a one-click install, and post-prize installs compound into Developer Funds revenue."
Surface: Devvit modqueue + post-submit trigger: every new image/link post fires a perceptual-hash + text-similarity check; high-confidence reposts su
P22
The Researcher
Tier B
ContextMod (context-mod)
⚠ 3-year dormant runtime; codebase intact
Treat the Devvit port as a *publishable case study* in rule-engine equivalence: every YAML rule from upstream ContextMod must produce a bit-identical mod-action verdict on a frozen corpus of 10K histo
"ContextMod ported to Devvit as a reproducible benchmark study: 95%+ rule-equivalence on a 10K-event golden corpus, sub-second p50 latency, lab-report UI, BibTeX-exportable evidence judges can cite."
Surface: Paper-style artifact bundle: dataset/method/result structure rendered as a moderator-readable 'lab report' inside the Devvit app — Figure 1
P23
The Game Designer
Tier A
u/RemindMeBot
RemindMeBot's job — schedule a future ping and deliver it on time — is already a quest loop in disguise. Reborn on Devvit as a 'Punctuality Engine', every 'RemindMe!' becomes a quest with stakes: XP o
"RemindMeBot reborn on Devvit as a Punctuality Engine: every reminder is a quest, ack on time for XP, stack streaks, climb the sub leaderboard."
Surface: Devvit custom post 'Quest HUD' embedded inline on the reminded comment + a sidebar custom post for the Punctuality Leaderboard. Live XP bar,
u/Flair_Helper2
Mod teams have been burned before — by silent mass-removes, runaway loops, irreversible bans on long-time contributors. This Devvit port of Flair_Helper2 ships brakes-on-by-default: every flair-trigge
"Flair_Helper2, ported to Devvit with the brakes on: every action shadow-mode by default, 30-day rollback per action, and a first screen that tells you not to install it."
Surface: 'Why you probably shouldn't install this yet' is the FIRST screen of the Devvit install/landing flow — four named failure modes (flair-rule
ContextMod
⚠ 3-year dormant runtime; codebase intact
ContextMod's power is locked behind a 600-line YAML DSL only senior mods can write. Port the rule engine 1:1 to Devvit (parity gate), then layer an Opus-4.7 chat overlay where any mod types 'flag post
"ContextMod, but you talk to it. Faithful Devvit port of the YAML rule engine, plus an Opus-4.7 chat that turns 'flag suspicious crosspost spam' into a tested, diff-previewed rule in 8 seconds."
Surface: Devvit custom-post 'Mod Console' tab anchored to the modqueue — primary interaction is a chat composer with @mention command palette (@rule,
u/Flair_Helper2
Port Flair_Helper2 to Devvit as the deterministic antithesis of LLM-ified moderation: every mod-action is a pure function of (post_flair_template_id, yaml_rule_line) with zero model calls and zero out
"Flair_Helper2 reborn on Devvit: every mod-action cites flair_helper.yaml:LINE, zero model calls at runtime, fully auditable end-to-end."
Surface: Devvit-native rulebook surface, rule-based and deterministic. PostFlairUpdate trigger fires the compiled rule; action ledger logs `flair_hel