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 ForgeyClap/claude-forgenpx agentmods add plugins/forgeyclap/claude-forge/forgegit clone --depth 1 https://github.com/ForgeyClap/claude-forgeWrote 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/forgeyclap/claude-forge/forge)<a href="https://agentmods.dev/plugins/forgeyclap/claude-forge/forge"><img src="https://agentmods.dev/badge/plugins/forgeyclap/claude-forge/forge.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
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 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "forge",
"displayName": "Forge V2",
"version": "2.0.0",
"description": "Zero-dependency multi-agent build, automation, review & delivery system that layers on Claude Code.",
"author": {
"name": "ForgeyClap",
"url": "https://github.com/ForgeyClap"
},
"homepage": "https://github.com/ForgeyClap/claude-forge#readme",
"repository": "https://github.com/ForgeyClap/claude-forge",
"license": "MIT",
"keywords": [
"multi-agent",
"orchestration",
"automation",
"code-review",
"build",
"scraping",
"rag",
"dashboard"
]
}
What it installs
The manifest is a name and a version. 11 skills travel with it, and installing the plugin installs all of them — 857 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill forge-prd A 87 tokens
- Skill gsap A 55 tokens
- Skill humanizer A 93 tokens
- Skill gsap-frameworks E 90 tokens
- Skill gsap-timeline E 61 tokens
- Skill gsap-scrolltrigger E 68 tokens
- Skill gsap-core E 128 tokens
- Skill gsap-plugins E 91 tokens
- Skill gsap-react E 68 tokens
- Skill gsap-performance E 52 tokens
- Skill gsap-utils E 64 tokens
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 · 25 lines scan A 424ed54664fe
forge is a plugin published in the GitHub repository ForgeyClap/claude-forge (2 stars, last pushed 1mo 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-09-03.
Other plugins, from other repositories
dx
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.
junior-flow
Helps junior developers create technical story markdown from a story tracker.
milestone-driver
Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…
context-optimization
Techniques for extending effective context capacity through compaction, observation masking, KV-cache optimization, and context partitioning. Double or triple effective context without larger models.
cc-research
Multi-agent deep research on Claude models: orchestrator -> parallel researcher subagents -> triangulate -> synthesize -> cite -> report. Built-in tools only (WebSearch, WebFetch, Read, Grep, Glob, Write, Task); no external research APIs or MCP servers.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.