Skip to content
View jothimani-rajendran's full-sized avatar
1 follower · 3 following

Achievements

Achievement: Pull Sharkx3Achievement: Pair ExtraordinaireAchievement: YOLOAchievement: Quickdraw

Achievements

Achievement: Pull Sharkx3Achievement: Pair ExtraordinaireAchievement: YOLOAchievement: Quickdraw

Highlights

  • Pro

Block or report jothimani-rajendran

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
.github/profile/README.md
open-coder-ai organisation mark: two gold chevrons held apart around a solid diamond, on a navy rounded square.

Open Coder AI

Governance as code for AI coding agents — and an honest account of where it holds.

Build for every AI coding agent at once: hooks, plugins and rules through one API, with governance and evidence on top. Claims match mechanisms.

The rule we hold ourselves to

A rule an agent reads is advice. A hook that exits non-zero is a control. Both belong in a repo, and the difference has to be visible.

What we build
agentseam the primitives — one handler API and a verified capability matrix across 16 agents
chock the compiler — one policy into git hooks, CI gates and native pre-tool hooks
chock-catalog the policies — 39, each labelled enforced or advisory, with replayed evals
context-report the evidence — a signed report of whether an agent artifact actually works
chock-threat-intel the threat ledger the catalog's policies answer to

Start here. If your repo receives agent-written commits, start with chock. If you build hooks or plugins, start with agentseam. If you maintain a catalog, start with context-report.

Help wanted. Open good first issues across the org.

Pinned Loading

  1. open-coder-ai/chock open-coder-ai/chock Public

    Governance-as-code for AI coding agents: author a policy once, enforce it on every agent (Claude, Copilot, Cursor, Codex) via git hooks, CI, and native controls.

    Python 3 1

  2. open-coder-ai/chock-catalog open-coder-ai/chock-catalog Public

    Policies that stop your coding agent from doing the thing you would have caught in review. The policy catalog for Chock: git-hook gates, command guards, and agent rules with replayed evals.

    Python 1

  3. .github .github Public

  4. open-coder-ai/agentseam open-coder-ai/agentseam Public

    The primitives layer for every coding agent — one handler API over per-agent hooks, instruction files, plugin packaging, and config.

    Python

  5. open-coder-ai/chock-threat-intel open-coder-ai/chock-threat-intel Public

  6. open-coder-ai/context-report open-coder-ai/context-report Public

    An open, signed report format for whether an agent plugin, hook, skill, or AGENTS.md actually works.

    Python