Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
/plugin marketplace add omerakben/code-oznpx agentmods add plugins/omerakben/code-oz/code-oz-disciplinegit clone --depth 1 https://github.com/omerakben/code-ozGrade A, and why
code-oz-discipline scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"name": "code-oz-discipline",
"description": "Advisory SDLC discipline skills (brainstorming, source-check, RED-first) for AI coding agents. Advisory only — not enforced gates; upsells to the code-oz engine for enforced gates and different-model review.",
"version": "0.21.2-alpha.0",
"author": { "name": "Ozzy (Omer Akben)", "url": "https://github.com/omerakben/code-oz" },
"homepage": "https://github.com/omerakben/code-oz",
"repository": "https://github.com/omerakben/code-oz",
"license": "MIT",
"keywords": ["code-oz", "advisory", "discipline", "tdd", "source-check", "brainstorming"],
"skills": "./skills"
}
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 12 lines scan A b5e678af4bab
code-oz-discipline is a plugin published in the GitHub repository omerakben/code-oz (2 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
open-plan-annotator
Plugin marketplace listing 1 plugin: open-plan-annotator.
open-plan-annotator
Interactive plan annotation UI: review, strikethrough, and comment on Claude's plans before approving. Fully local, no external services.
loopat-builtin
Loopat platform-shipped plugins.
loopat
Built-in loopat platform skills (promote, help).
agent-teams
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams.
wt-local
Local marketplace populated by wta.