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 XRenSiu/claude-code-forgenpx agentmods add plugins/xrensiu/claude-code-forge/loopergit clone --depth 1 https://github.com/XRenSiu/claude-code-forgeGrade A, and why
looper 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.
How it starts
The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "looper",
"description": "Looper — a system's design contract in both directions: forward-author the product world from a raw idea, or reverse-engineer it from existing code and failure memory. `/psl` turns one experiential / semantically-fuzzy requirement (plus optional materials) into a complete Product Specification Language document — six derivation-ordered layers (Vision / Mental Model / Domain Model that must overturn the naive schema / State Machine / Workflow split into Σ facts + φ disambiguation criteria, never Step 1-2-3 / behavioral Acceptance in ask-X-get-Y form) — under a three-provenance honesty discipline (surface engine world knowledge / elicit private load-bearing slots one topic at a time with recommended lettered answers / seam everything unanswerable into Open Questions, never default-fill), a dual-track entry gate (deterministic requirements get told 'PRD suffices' instead of a fabricated world), and a hard delivery contract (never refuses for lack of info), mechanically pre-gated by verify_psl.py (rejects missing layers, named-step Workflow, non-behavioral Acceptance, absent Open Questions). `/dos-extract` deductively recovers a Design Ontology Spec (DOS): a 12-section dos.yaml (objects / relationships / constitutional rules / bounded contexts / agent guidelines) + decisions.md audit trail, applying four classification judgments (object vs UI vs impl vs rule; same-object-vs-two; constitution vs policy; single vs multi context) that a naive noun-scan skips, with a mechanical pre-gate (verify_dos.py rejects UI/impl-suffixed names, undeclared relationship refs, >7 objects, empty open_questions) plus a human sign-off seam. `/invariant-extract` abductively recovers ONE Territory's □-class resident invariants from the failures it paid for (a violation is the most reliable signal an invariant exists) and deductively from code execution points, emitting a named-field invariant card (statement / strength / aspect / channel / provenance / oWhat 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 · 35 lines scan A 0c9d290444b2
looper is a plugin published in the GitHub repository XRenSiu/claude-code-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-08-31.
Other plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.