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/clomia/claude-automataWrote 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/clomia/claude-automata/refine)<a href="https://agentmods.dev/plugins/clomia/claude-automata/refine"><img src="https://agentmods.dev/badge/plugins/clomia/claude-automata/refine/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/clomia/claude-automata/refine"><img src="https://agentmods.dev/badge/plugins/clomia/claude-automata/refine.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
refine 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 20d 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": "refine",
"version": "0.15.0",
"description": "Repository debt elimination — heavyweight multi-agent workflows that cross-examine findings into consensus, then apply only the highest-ROI fixes: code, docs",
"author": {
"name": "clomia",
"email": "[email protected]",
"url": "https://github.com/clomia"
},
"homepage": "https://claude-automata.clomia.com/",
"repository": "https://github.com/clomia/claude-automata",
"license": "Apache-2.0",
"keywords": [
"refactoring",
"architecture",
"documentation",
"antipattern",
"workflow",
"multi-agent",
"code-quality",
"autonomy"
],
"dependencies": ["version-up-alert"]
}
What it installs
The manifest is a name and a version. 2 skills, 1 agent travel with it, and installing the plugin installs all of them — 126 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.
- 20d ago Changed ede4d966a031
- 1mo ago First seen · 25 lines scan A c8a5885dc58a
refine is a plugin published in the GitHub repository clomia/claude-automata (14 stars, last pushed 12d ago), licensed Apache-2.0. 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-30.
Other plugins, from other repositories
technology
Architecture, engineering delivery, development discipline, debugging, review, and AI and automation systems.
brooks-lint
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix).
graph-it-live
Dependency, call-graph, impact, and architecture analysis for codebases.
logic-lens
Logic-first code review using semi-formal execution tracing. Surfaces behavioral bugs, type contract breaches, boundary blindspots, and interprocedural semantic mismatches — the logic errors that cause production incidents in syntax-clean code.
logic-lens
Logic-first code review using semi-formal execution tracing. Surfaces behavioral bugs, semantic errors, and runtime failures that linters miss.
plugin-dev
Plugin development tools: scaffold new plugins, validate SKILL.md frontmatter, audit hooks for silent failures.