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 luiseiman/dotforgenpx agentmods add plugins/luiseiman/dotforge/marketplacegit clone --depth 1 https://github.com/luiseiman/dotforgeGrade A, and why
dotforge 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": "dotforge",
"owner": {
"name": "Luis Eiman",
"email": "[email protected]"
},
"metadata": {
"description": "Configuration governance for Claude Code — bootstrap, audit, sync, and evolve .claude/ across projects",
"version": "2.9.0"
},
"plugins": [
{
"name": "dotforge",
"source": ".",
"description": "Configuration governance for Claude Code — 18 skills, 7 agents, 16 stacks, 9 hooks, audit scoring (0-10), and practices pipeline.",
"version": "2.9.0",
"author": {
"name": "Luis Eiman"
},
"homepage": "https://github.com/luiseiman/dotforge",
"repository": "https://github.com/luiseiman/dotforge",
"license": "MIT",
"keywords": ["configuration", "audit", "bootstrap", "sync", "hooks", "rules", "agents", "stacks", "practices"],
"category": "developer-tools",
"tags": ["configuration-management", "governance", "multi-project"]
}
]
}
What ships with it
2 files beside marketplace.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.
- yesterday First seen · 29 lines scan A 0a7c64210453
dotforge is a plugin published in the GitHub repository luiseiman/dotforge (8 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
ops
Plugin marketplace listing 1 plugin: ops.
ops
Structured non-code project management for Claude Code: planning, execution, knowledge persistence, and autonomous work loops for research, strategy, and content projects. 9 skills, 5 agents, 7 commands.
factory-kit
Portable Factory Kit workflows for software delivery.
factory-kit
Portable software-factory skills, Claude compatibility workflows, and Linear integration.
claude-hangar-dev
Development marketplace for Claude Hangar plugin.
skill-olympus
Twelve Greek gods. One command. A working SaaS. 100 public skill sources with a lightweight entrypoint-only registry, 42 optional agent references, and native-agent orchestration for Claude Code, Codex CLI, Gemini CLI, and Grok Build.