aizee SKILL.md skillA

aizee from m3taz-ahmed/aizee is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add m3taz-ahmed/aizee/aizee@git:20261027.67e2195

Pins git:20261027.67e2195 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
m3taz-ahmed/aizee
Path
SKILL.md
Versions recorded
2
Latest version
git:20261027.67e2195, committed Oct 27, 2026
First version recorded
Oct 27, 2026
Size
3,332 bytes
Repository stars
6
License
MIT

Sovereign AI engineering control plane — governed CLI + MCP tools that enforce policy, budget, guardrails, and audit on every agent action. Use when an agent needs enforcement (not advice) over LLM traffic, tool calls, memory, and workflows.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# aiZee — governed agent operations

aiZee is a policy layer for AI coding agents. It is NOT an LLM, code
generator, or CI/CD replacement — it sits on the action path and enforces
rules so agents cannot bypass them.

## When to use

- Before writing/modifying code: check policy via `aizee check <action>`.
- Before calling an LLM: route through `aizee gateway serve` (failover +
  enforced gates on the traffic path).
- When exploring a codebase: `aizee find "<need>"` and `aizee goal "<obj>"`
  map natural language to skills/workflows/steps.
- When diagnosing the environment: `aizee doctor` (CLI) or `aizee_doctor`
  (MCP) returns `verdict` + ordered `next_steps`.
- When tracking a change: `aizee spec propose <name>` creates an
  OpenSpec-style change folder (proposal/design/tasks); `aizee spec
  archive <name>` lands it.

## Command surface

| Command | Purpose |
|---|---|
| `aizee doctor [--json]` | Structured health verdict + `Run:`/`Guidance:` steps |
| `aizee check <action>` | Policy + budget pre-flight for one action |
| `aizee find <query>` | NL search over skills/workflows/tech-stack |
| `aizee goal <objective>` | Map goal → best workflow + steps |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add m3taz-ahmed/aizee/aizee@sha256:4879757a48ea6786

The line at the top of this page pins the label git:20261027.67e2195, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_vsotdr6trljmhwfq.svg)](https://markdownregistry.com/a/art_vsotdr6trljmhwfq)

3 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in m3taz-ahmed/aizee/aizee since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of aizee from somewhere else? Ask it: where did my aizee come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 2 versions of this file, all committed on Oct 27, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261027.67e2195 latest2026-10-27 67e2195 3,332 BA view · diff
git:20261027.36201712026-10-27 3620171 3,111 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (3332 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

m3taz-ahmed/aizee · 6 stars · license MIT · pushed 2026-11-15 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_vsotdr6trljmhwfq
GET https://markdownregistry.com/api/v1/resolve?ref=m3taz-ahmed/aizee/aizee
GET https://markdownregistry.com/api/v1/blob/4879757a48ea67863395ee0db06f60fb88a9f1f907ef0bf7018530b51a064d7d

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from m3taz-ahmed/aizee

CLAUDE.md@.claude CLAUDE.md file
m3taz-ahmed/aizee · .claude/CLAUDE.md
git:20261107.4ae71c4 · audit A · 6 stars
global-os SKILL.md skill
m3taz-ahmed/aizee · .claude/skills/global-os/SKILL.md · Load aiZee context layers and route to the correct workflow.
git:20260817.b0f7e30 · audit A · 6 stars
graphify SKILL.md skill
m3taz-ahmed/aizee · .claude/skills/graphify/SKILL.md · Query the graphify knowledge graph before reading files. Trigger /graphify.
git:20260714.353f8b0 · audit A · 6 stars
aizee Cursor rule
m3taz-ahmed/aizee · .cursor/rules/aizee.mdc · aiZee canonical adapter
git:20261107.4ae71c4 · audit A · 6 stars
git Cursor rule
m3taz-ahmed/aizee · .cursor/rules/git.mdc · Git rules. Conventional commits, atomic staging, no force push.
git:20260714.353f8b0 · audit A · 6 stars
graphify Cursor rule
m3taz-ahmed/aizee · .cursor/rules/graphify.mdc · Graphify knowledge graph first. Use before grep/read.
git:20260714.353f8b0 · audit A · 6 stars
mcp Cursor rule
m3taz-ahmed/aizee · .cursor/rules/mcp.mdc · MCP usage. Context7 for docs, graphify for codebase.
git:20260817.b0f7e30 · audit A · 6 stars
memory Cursor rule
m3taz-ahmed/aizee · .cursor/rules/memory.mdc · Memory sync. Read MEMORY.md at start, update after milestone.
git:20260811.7220bad · audit A · 6 stars
quality Cursor rule
m3taz-ahmed/aizee · .cursor/rules/quality.mdc · Code quality. 0 linter warnings, SOLID/DRY/KISS, strict typing.
git:20261006.fcbea87 · audit A · 6 stars
security Cursor rule
m3taz-ahmed/aizee · .cursor/rules/security.mdc · Security rules. Validate inputs, no leaks, no wildcard CORS.
git:20260926.b417e97 · audit A · 6 stars
tech-stack Cursor rule
m3taz-ahmed/aizee · .cursor/rules/tech-stack.mdc · Tech-stack version gating. Detect exact version from lockfile.
git:20260714.353f8b0 · audit A · 6 stars
global-os SKILL.md skill
m3taz-ahmed/aizee · .devin/skills/global-os/SKILL.md · Load aiZee context layers and route to the correct workflow.
git:20260817.b0f7e30 · audit A · 6 stars

Every file in m3taz-ahmed/aizee

Other files named aizee

aizee Cursor rule
m3taz-ahmed/aizee · .cursor/rules/aizee.mdc · aiZee canonical adapter
git:20261107.4ae71c4 · audit A · 6 stars

Browse by kind, by grade A, or by owner.