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/sethdford/claude-skillsWrote 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/sethdford/claude-skills/architecture-governance)<a href="https://agentmods.dev/plugins/sethdford/claude-skills/architecture-governance"><img src="https://agentmods.dev/badge/plugins/sethdford/claude-skills/architecture-governance/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/sethdford/claude-skills/architecture-governance"><img src="https://agentmods.dev/badge/plugins/sethdford/claude-skills/architecture-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
architecture-governance 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 8d 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": "architecture-governance",
"version": "1.0.0",
"description": "Establish architecture governance, design fitness functions, manage tech debt, and ensure compliance. Build sustainable architecture practices.",
"author": { "name": "Seth Ford" },
"keywords": [
"architect",
"governance",
"fitness-function",
"compliance",
"tech-debt"
],
"license": "MIT"
}
What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 242 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.
- 8d ago First seen · 15 lines scan A 7461e594336c
architecture-governance is a plugin published in the GitHub repository sethdford/claude-skills (39 stars, last pushed 6mo 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-30.
Other plugins, from other repositories
repomix-explorer
AI-powered repository analysis agent using Repomix CLI. Analyzes local and remote repositories intelligently by running repomix commands, then reading and searching the generated output files to answer questions about code structure, patterns, and content.
open-pr
Review GitHub Pull Requests and GitLab Merge Requests across many stacks, learning each repo's own conventions over time and posting one review via that vendor's own CLI.
code-review
Code review plugin.
mneme
Enforce architectural decisions and engineering standards before Claude Code writes changes.
frontier
Standards written and audited by Claude Fable 5: make Opus, Sonnet, GPT, or Gemini produce work close to its bar. 21 craft rubrics, best-of-N candidates, convergence sweeps, a taste gate with permanent distillation.
pragma
Deterministic linting hooks, semantic code validators, and a multi-LLM advisory council. Enforces coding rules mechanically — not by suggestion.