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/JeonJe/claude-pluginsWrote 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/jeonje/claude-plugins/arch-patterns)<a href="https://agentmods.dev/plugins/jeonje/claude-plugins/arch-patterns"><img src="https://agentmods.dev/badge/plugins/jeonje/claude-plugins/arch-patterns/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/jeonje/claude-plugins/arch-patterns"><img src="https://agentmods.dev/badge/plugins/jeonje/claude-plugins/arch-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
arch-patterns 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": "arch-patterns",
"version": "1.0.0",
"description": "Production-tested architecture rules for feature development: Spring layered/DDD boundaries with domain-event and exception-ladder design, and Vue/Nuxt MVVM with query-composable wrapping and component quality bars",
"author": {
"name": "JeonJe",
"url": "https://github.com/JeonJe"
},
"repository": "https://github.com/JeonJe/claude-plugins",
"license": "MIT",
"keywords": ["claude-code", "plugin", "architecture", "ddd", "spring", "vue", "nuxt", "mvvm", "patterns"],
"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 — 298 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 · 14 lines scan A 0e56b4cf516f
arch-patterns is a plugin published in the GitHub repository JeonJe/claude-plugins (3 stars, last pushed 2mo 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
component-patterns-plugin
Reusable UI component patterns for implementing common features across different frameworks and tech stacks.
api-plugin
API integration and testing - REST endpoints, client generation, contract testing.
api-architect
API design, documentation, and testing with OpenAPI spec generation.
api-benchmarker
API endpoint benchmarking and performance reporting.
api-tester
Test API endpoints and run load tests against services.
backend-architect
Backend service architecture design with endpoint scaffolding.