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.
/plugin marketplace add davisjam/model-based-agentic-software-engineeringnpx agentmods add plugins/davisjam/model-based-agentic-software-engineering/marketplacegit clone --depth 1 https://github.com/davisjam/model-based-agentic-software-engineeringGrade A, and why
agent-governance-mechanisms 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 yesterday.
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": "agent-governance-mechanisms",
"owner": {
"name": "James C. Davis",
"email": "[email protected]"
},
"metadata": {
"description": "The agent-governance-mechanisms catalogue, distributed as an installable Claude skill.",
"version": "0.1.0"
},
"plugins": [
{
"name": "mage",
"source": "./plugin/mage",
"description": "Two partner skills for agent-fleet repos — self-governance (harden: audit for missing guardrails, or convert a recurring failure into a durable control) and self-operations (operate: run the substrate, route breaks to their fix). Grounded in the agent-governance-mechanisms catalogue."
}
]
}
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.
- yesterday First seen · 19 lines scan A 539bc707a53b
agent-governance-mechanisms is a plugin published in the GitHub repository davisjam/model-based-agentic-software-engineering (18 stars, last pushed yesterday), 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
claude-code-tips
Developer experience essentials: GitHub Actions debugging, conversation half/quarter-cloning, context handoffs, research (Reddit and Hacker News), private GitHub search, and Claude Code version checks.
the-loop
Plugin marketplace listing 1 plugin: the-loop.
the-loop
An opinionated product-development-lifecycle harness that lets coding agents deliver work items end-to-end, with minimal human intervention, through a predictable loop of plan, execute, self-review, critic-review and escalate.
claude-bestpractice
Enforcement, memory and parallel-session coordination for solo founders running several Claude Code sessions on one repository.
ooda-loop
Plugin marketplace listing 1 plugin: ooda-loop.
mappamind-plugins
Grounded, visual architecture-impact cards for AI coding sessions.