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/qwerfunch/claddingWrote 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/qwerfunch/cladding/gemini-cli)<a href="https://agentmods.dev/plugins/qwerfunch/cladding/gemini-cli"><img src="https://agentmods.dev/badge/plugins/qwerfunch/cladding/gemini-cli/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/qwerfunch/cladding/gemini-cli"><img src="https://agentmods.dev/badge/plugins/qwerfunch/cladding/gemini-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cladding 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": "cladding",
"version": "0.10.1",
"description": "Reference implementation of the Ironclad standard — multi-agent dev harness for Gemini CLI. Exposes spec validation, drift detection, 15 Iron Law stages, and 5 agent personas as custom commands + an auto-launched MCP server.",
"contextFileName": "GEMINI.md",
"mcpServers": {
"cladding": {
"command": "clad",
"args": ["serve"]
}
}
}
What ships with it
3 files beside gemini-extension.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed 890a6d8d1d5f
- 1mo ago Changed abf3af2e2b2c
- 1mo ago First seen · 13 lines scan A 8851b0ac89a3
cladding is a plugin published in the GitHub repository qwerfunch/cladding (16 stars, last pushed 1mo 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-09-06.
Other plugins, from other repositories
multi-cursor
Official Cursor SDK coding harness.
lid-experimental
Experimental LID skills with opt-in installation and explicit lifecycle (promotion or retirement). Layers on top of linked-intent-dev and arrow-maintenance.
commander-hub marketplace
Plugin marketplace listing 1 plugin: commander.
dekko
Static code map for LLM agents. /map parses the repository with tree-sitter into MAP.md and map.json (every file, function, signature, type, and call edge) without spending model tokens; an 18-tool MCP server (searchcode, outline, querysymbol, getcallers, workset, impactedtests, ...) answers structural questions fr.
superb
Personal skill collection for Claude Code and Codex, invoked as superb: . setup installs what the others need; craft turns a vague product idea into a decision-rich brief; pipeline v2 drives a settled idea through approved file-backed plans and durable execution state to a finished branch; pipeline-auto does the.
ratatoskr
A communication layer for your AI coding agent: plain language, no jargon, no invented timelines, and one clear yes before anything irreversible — shaping how the agent talks to you, not how it works.