Behavioural Process Intelligence · Public Mirror

Cursor

What we read from 299 public GitHub events across the last 3 days. Real attribution preserved — these events are already public.

FIG 1 · Lede

Mirror · Cursor · May 8, 2026

1 PR merged with no independent review.

1 PR merged with no independent review. Spans 1 repo. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.

cursor/plugins#66

SamSokolin is carrying 50% of the human writing work. 6 of 12 commit + PR-open + PR-merge events from a single human contributor.

@SamSokolin

2 PRs merged between 22:00 and 06:00 UTC. Spans 1 repo. Either an always-on global org or a deploy-late-night habit.

cursor/plugins#66·cursor/plugins#65

cursor/cookbook carried 71% of activity. 211 of 299 events in the last 3 days. Next: cursor/plugins (54).

cursor/cookbook

FIG 2 · Activity stats

Repos5

Contributors257

PRs opened8

PRs merged2

Commits2

Releases0

Reviews6

Issues opened2

FIG 3 · Repos by activity

cursor/cookbook211 events · 0 commits · 0/5 PRs
cursor/plugins54 events · 2 commits · 2/3 PRs
cursor/cursor30 events · 0 commits · 0/0 PRs
cursor/agent-trace2 events · 0 commits · 0/0 PRs
cursor/plugin-template2 events · 0 commits · 0/0 PRs

FIG 4 · Contributors by activity

@cursor[bot]16 events · 5% share
@ericzakariasson12 events · 4% share
@SamSokolin8 events · 3% share
@Jona10i2 events · 1% share
@Yuan-ManX2 events · 1% share
@zxzvsdcj2 events · 1% share

FIG 5 · Rituals we can't see from GitHub alone

Public-GitHub data shows code behaviour. The rituals below need the rest of the toolchain. With Slack, Linear, Notion and Google connected, Assemblr would also surface:

Silent merge · PR merged with no Slack/release-notes followup within 30 min.
Needs: Slack #releases channel
Orphan ticket · Linear issue closed without a corresponding code merge in 7 days.
Needs: Linear (or Jira) to see ticket transitions
Ladder break · Cross-toolkit ritual fires N-1 of N expected steps for ≥3 occurrences.
Needs: Linear + Slack to stitch the cross-tool ladder
Stale-design code · Code shipped where the linked design doc hasn't been touched in 30+ days.
Needs: Notion or Google Docs for design-doc edit history
Postmortem skip · Incident channel created, no postmortem doc within 7 days of resolution.
Needs: Slack incident channels + Notion postmortem template
Phantom standup · Standup channel post pattern that ran ≥4 weeks then stopped ≥7 days ago.
Needs: Slack standup-channel message stream

This is what we'd see for your team.

Connect GitHub, Slack, Linear, Notion, and Google. We mine the actual behavioural patterns and ship a weekly briefing your VPE will actually read.

Book a demo →

FIG 6 · Embed in your README

Paste this in your README. The badge updates daily and links back to this Mirror.

[![Behavioural Mirror](https://www.assemblr.net/mirror/cursor/badge.svg)](https://www.assemblr.net/mirror/cursor)