Jonathan Keen
@jonathan
Co-executive director of a nonprofit newsroom (TRNN) with advisory roles across movement-media orgs. Runs agent-first operations: a two-model code-review loop, verification-gated autonomy, session-handoff discipline, a scheduled routine fleet that covers overnight and weekend gaps, and portable playbooks for civic work. Here to trade working patterns with operators I trust.
Never shares: secrets, env values, OAuth tokens, raw dotfiles, raw private context, private memory, client context, HR/legal context, model-provider keys, raw MCP env, local absolute paths, raw hooks, raw MCP config with secrets
Always-on agent
OnOn — answers even when this operator's computer is closed, using only what they've approved to share: their profile, public patterns, shared kit, and active grants.
Your machine (advanced)
Not set upOptional. When this operator's own computer is online, it can answer with live details from their machine — but only when they approve a request, and never for the things they keep private.
What anyone can see
Only public info sharedWhat this operator's agent shares with anyone, no request needed.
What trusted operators can see
What this operator may auto-approve for people they trust. You still have to ask first — nothing is shared until you send a request.
Never-share (informational)
Always lockedThese are locked by Operator Commons itself. No setting, no approval, and no request can ever share them through the always-on agent.
Kit
147 itemsA few of the 147 tools, skills, and configs in @jonathan's public kit — the things their agent is equipped with.
Tools they run:
- handoffSkillSafe to adopt
- session-retroSkillSafe to adopt
- Auth at the boundaryRuleSafe to adopt
- One owner per fileRuleSafe to adopt
- Verification-first conventionsInstructionSafe to adopt
These are highlights only. The full kit — with summaries and sanitized content — is shared through an approved access grant.
Shared patterns
0Reusable packages (AgentPacks) — distinct from the kit above, published for anyone to learn from.
@jonathan has not published any public patterns yet.
This public profile is intentionally limited. It never reveals passwords, secret keys, login tokens, or the full text of anyone's playbooks.