verifiable-gates
v0.5.0Production-discipline rules for a software project, each carrying the real incident that produced it — the verifiable-gates skill, rendered from rules.yaml; nine of the rules are decided mechanically by the bundle's own scanners once a project installs it (pip install verifiable-gates; python -m verifiable_gates.install). Installing this plugin lands the whole repository and adds a PostToolUse hook that runs the installed doctor after every Edit or Write — off by default; on with VERIFIABLE_GATES_AT_EDIT=1 in the project's .claude/settings.json under env. It reports and refuses nothing.
By Sayam SriphuaLicense: Apache-2.0 AND CC-BY-4.00 GitHub starsUpdated 2 weeks ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 6, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install verifiable-gates for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install verifiable-gates@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/sayam/verifiable-gatesClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .claude-plugin/plugin.json└── skills/verifiable-gates/SKILL.md
Included Skills1
Production-discipline rules for a software project — each one carrying the real incident that produced it, nine of them decided mechanically by the bundle's own scanners. Use when writing or reviewing code in a project that has installed the verifiable-gates bundle (a tools/gates_doctor.py exists), when asked which rules bind a repository, or when a change touches a service layer, templates, a Dockerfile, a CI workflow, an ADR index, or a gate registry.
Plugin manifests1
{
"name": "verifiable-gates",
"displayName": "verifiable-gates",
"version": "0.5.0",
"description": "Production-discipline rules for a software project, each carrying the real incident that produced it — the verifiable-gates skill, rendered from rules.yaml; nine of the rules are decided mechanically by the bundle's own scanners once a project installs it (pip install verifiable-gates; python -m verifiable_gates.install). Installing this plugin lands the whole repository and adds a PostToolUse hook that runs the installed doctor after every Edit or Write — off by default; on with VERIFIABLE_GATES_AT_EDIT=1 in the project's .claude/settings.json under env. It reports and refuses nothing.",
"author": {
"name": "Sayam Sriphua",
"url": "https://github.com/sayam"
},
"homepage": "https://github.com/sayam/verifiable-gates",
"repository": "https://github.com/sayam/verifiable-gates",
"license": "Apache-2.0 AND CC-BY-4.0",
"keywords": [
"software governance",
"AI-assisted development",
"continuous integration",
"secure software development",
"developer experience"
],
"skills": "./skills/"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[verifiable-gates on Agent Plugins Marketplace](https://pluginsmp.com/plugins/verifiable-gates)