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/basher83/lunar-claudeWrote 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/basher83/lunar-claude/repo-forge)<a href="https://agentmods.dev/plugins/basher83/lunar-claude/repo-forge"><img src="https://agentmods.dev/badge/plugins/basher83/lunar-claude/repo-forge/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/basher83/lunar-claude/repo-forge"><img src="https://agentmods.dev/badge/plugins/basher83/lunar-claude/repo-forge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
repo-forge 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 2mo 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": "repo-forge",
"version": "0.3.0",
"description": "Project setup and validation toolkit for standardizing repos with mise, hk, and changelog tooling across Python, Rust, Bun/TypeScript, Terraform, and Ansible projects",
"author": {
"name": "basher83",
"email": "[email protected]"
},
"keywords": [
"mise",
"hk",
"gitignore",
"git-cliff",
"changelog",
"project-setup",
"validation",
"python",
"rust",
"bun",
"typescript",
"terraform",
"ansible"
]
}
What it installs
The manifest is a name and a version. 1 skill, 1 command travel with it, and installing the plugin installs all of them — 34 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.
- 2mo ago First seen · 25 lines scan A 718ff31785c2
repo-forge is a plugin published in the GitHub repository basher83/lunar-claude (23 stars, last pushed today), 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-09-03.
repo-forge compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| repo-forgebasher83/lunar-claude | Plugin | 23 | today | MIT | A | — | Claude Code |
| githubcursor/plugins | Plugin | 16k | today | none | A | — | Cursor |
| github-actions-pipeline-buildercuriositech/some_claude_skills | Plugin | 264 | 4d ago | MIT | A | — | Claude Code |
| mcp-gitlabvish288/mcp-gitlab | Plugin | 7 | today | MIT | A | — | Gemini CLI |
| nyannthettwe/nyann | Plugin | 7 | 2d ago | MIT | A | — | Claude Code |
| charonANcpLua/ancplua-claude-plugins | Plugin | 6 | today | MIT | A | — | Claude Code |
| forgedockRapierCraftStudios/ForgeDock | Plugin | 119 | today | AGPL-3.0 | A | — | Claude Code |