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.
git clone --depth 1 https://github.com/omerakben/code-ozWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/omerakben/code-oz/code-oz-discipline)<a href="https://agentmods.dev/plugins/omerakben/code-oz/code-oz-discipline"><img src="https://agentmods.dev/badge/plugins/omerakben/code-oz/code-oz-discipline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/omerakben/code-oz/code-oz-discipline"><img src="https://agentmods.dev/badge/plugins/omerakben/code-oz/code-oz-discipline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 1mo ago.
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 it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 89 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago 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 4mo 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
nw
nWave: AI-powered workflow framework — 23 agents, 98+ skills, TDD enforcement, and wave-based development methodology for Claude Code.
mattpocock-skills
Skills adapted from Matt Pocock's public collection.
assay
Opens a page you changed, drives every control it offers, and reports what it did and what happened. One line every time, clean or not.
rudder
Maintain a device-local spec from coding-session intent, then generate focused unit tests with your existing coding agent.
epic
3 commands + 25 auto-trigger skills + self-evolving agent harness. Less to remember, more automation.
red-handed
Your agent said the tests pass. This checks that a test actually ran. Installing turns on two hooks: one strips the tail or grep that eats test results before a test command runs, one audits the session against git the moment it ends and warns only when something was caught. It also adds /red-handed:audit and…