ModMochi

ModMochi is a moderation tool that gives your mod team user trust scoring, report pattern detection, and weekly mochi mod mail all from the overflow menu you already use.

Comment

ModMochi

Soft on the outside, smart on the inside.

ModMochi is a moderation intelligence tool that gives Reddit mod teams trust scoring, collision prevention, report pattern detection, and a Mochi info report all from the overflow menu they already use.

Inspiration

I started by reading the Discord ModChat and the r/ModSupport to understand a bit more about what moderators might find useful. There was a lot to unpack there. I thought the overwhelming sentiment was that mods want better information to make their own decisions not more automation making decisions for them. That insight shaped everything about ModMochi: it surfaces context, it doesn't take action on its own. Ai helped find other academic research on Reddit moderation. study 1 A CHI 2026 study surveying 110 active Reddit moderators across 400+ subreddits found that mods frequently leave the mod queue to gather context on users, losing time and focus.

study 2 A separate Cornell CSCW 2025 study found that 67% of moderators cited social dynamics as their top challenge, and that enforcement was "nearly impossible" without reliable detection tools. Most strikingly, nearly 75% of mod teams reported instances where multiple moderators simultaneously work on the same item without knowing. I read and tried to validate some ideas. The existing Devvit ecosystem has pieces ReputatorBot does manual reputation via !thanks commands, sub-stats-bot dumps tables to wiki pages, modqueue-tools sends Discord alerts. But nobody had built an integrated system that combines user intelligence, team coordination, workflow automation, and pattern detection in one install. AutoMod. AutoMod is a rule engine — "if title contains X, remove it." It's stateless and pattern-based. A lot of subs use it.

ModMochi fills the gap it knows who the user is, whether they're a repeat offender, what other mods are currently reviewing, and whether your sub is being report-bombed. They work together.

What it does

6 menu items, 5 integrated features, zero new screens to learn. Check User - Instant Context Card Click ⋯ on any post or comment → Mochi: Check User → see the author's trust score (0-100), risk level (🟢🟡🔴🟣), account age, karma, removal/approval/ban counts, mod note count with label breakdown (SPAM_WARNING: 3, HELPFUL_USER: 2). Everything you need to make a decision in 3 seconds then use Reddit's native tools to act.

Claim System No More Collisions Click Mochi: Claim Item before reviewing. Other mods see "Already being reviewed by u/YourName (3m ago)." Release early with Mochi: Release Claim. See what the whole team is working on with Mochi: View Team Claims (shows post titles and comment snippets, not raw IDs). Claims auto-expire after a configurable window (default 10 min).

Report Pattern Detection Detects spikes (5+ reports on one item in 10 min) and clusters (15+ total reports in 10 min). Available from the ⋯ menu on any post, comment, or the subreddit menu. Automated scanner runs every 5 minutes and sends modmail alerts with a 30-minute cooldown to prevent alert fatigue.

Trust Score Engine Runs silently from the moment of install. Every post and comment creates a user profile. Every mod action updates the score. Deleted or suspended accounts retain their history with a 🟣 indicator. Scores recalculate with live Reddit data on every Check User lookup.

Weekly Report Every Sunday at 9am modmail with total actions, removals, approvals, bans, average review time, and the top 5 repeat offenders. Zero effort required.

Welcome Message On install, the mod team receives a modmail explaining every feature and how to configure settings. No guesswork.

How we built it

ModMochi is built on the Devvit Web architecture using TypeScript, Hono, and Vite, following the official devvit-template-mod-tool-devvit-web template.

The architecture has three layers:

Core engines (src/core/) four modules that share a single Redis data layer:

  • trust-engine.ts scoring algorithm, profile CRUD, username reverse lookup, weekly stats tracking, and the context card builder
  • claims.ts Redis key-with-TTL pattern for collision prevention, active claims sorted set for team view
  • report-detector.ts sorted set of report timestamps with sliding window analysis

Route handlers (src/routes/) Hono endpoints for menu items, event triggers, and scheduled jobs. Each route handler is thin, it validates input, calls the appropriate core engine, and returns a UiResponse.

Configuration (devvit.json)"6 menu items, 6 triggers"2 scheduler tasks, and 5 configurable subreddit settings, all declared declaratively.

Key technical decisions:

  • Redis hashes for user profiles (O(1) field access), sorted sets for trust leaderboard and report timeline
  • Username reverse lookup index so deleted accounts can still be found by name
  • All weekly stats auto-expire after 2 weeks, report data after 1 hour, claims after the configured TTL

Challenges we ran into

I have some experience developing games on Reddit this is the first time attempting to make a mod tool. I looked at r/ModSupport to see what issues people run into. There’s a lot to sift through and understand what might be useful for other mods. Some things are not possible to build i saw a lot of requests for Cross-sub history. This is a hard limitation. Then I settled on a few of these specifically : "every mod interaction needs context.” with the Check User feature you have access to the instant history without leaving the queue.

Accomplishments that we're proud of

The check User feature helps mods get context about a user quickly. Usually they currently have to dig for context across multiple screens. The trust score surviving account deletion. When a user deletes their account, most tools lose all context. ModMochi keeps their profile in Redis via a username reverse lookup index, so a mod checking a deleted user's post still sees "🟣 Deleted/Suspended Removals: 4, Bans: 1." The history doesn't disappear with the account.

Zero learning curve. Everything lives in the ⋯ menu mods already use hundreds of times a day. No new pages, no dashboards, no commands. We deliberately killed the dashboard feature we originally designed because the research told us mods want to act faster, not look at charts.

What we learned

It was important to do research for this hackathon, there was a lot of information to read through. I don’t think one size fits all. That was the idea I had at the start. Mods want to make their own calls with better information. ModMochi is opinionated about surfacing context, not about taking action. The "mods leave the queue to gather context" finding defined the Check User feature. Without the research, we would have built something that looked impressive but didn't solve real problems.

What's next for ModMochi

I’d like to get user feedback and improve it some more but the following are some ideas I think that could be useful. **Trust score decay is the priority a scheduled job that gradually moves scores back toward neutral over time, so a single bad week doesn't permanently define a user. It rewards sustained good behaviour and addresses the fairness concern that mods will inevitably raise.

Bulk actions. During brigades, mods need to act on 20 items at once, not one at a time. A "select multiple → apply chain" workflow would be the biggest time saver for large subs under attack.

Report accuracy tracking. If a user's reports consistently lead to removals, their reports should surface higher in the queue. If a user's reports are consistently dismissed, flag them as a potential report abuser.

ModMochi because moderating shouldn't feel like guesswork.

Built With

Share this project:

Updates