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 anilcancakir/claude-code-pluginsnpx agentmods add plugins/anilcancakir/claude-code-plugins/project-optimizergit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginsGrade A, and why
project-optimizer 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 2d 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": "project-optimizer",
"version": "1.1.0",
"description": "Create project.md (PRD), brand.md (brand guidelines), and CLAUDE.md (technical config) for any project. Interactive workflow with audit, archetype-based branding, and stack-specific optimization. Supports Laravel, Flutter, Vue2/3, Nuxt2/3, TailwindCSS, Alpine.js, and more.",
"author": {
"name": "Anilcan Cakir",
"email": "[email protected]"
},
"homepage": "https://github.com/anilcancakir/claude-code-plugins",
"repository": "https://github.com/anilcancakir/claude-code-plugins",
"license": "MIT",
"keywords": [
"claude-code",
"claude-md",
"project-brief",
"prd",
"brand-guidelines",
"design-system",
"optimization",
"laravel",
"flutter",
"vue",
"nuxt",
"tailwindcss",
"alpine"
],
"skills": "./skills/"
}
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.
- 2d ago First seen · 29 lines scan A cf391f4c7a3e
project-optimizer is a plugin published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 7mo 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
evolving-lite
Self-evolving Claude Code system that learns from corrections, manages context, and improves every session.
project-brain
Folder structure + collaboration protocol so AI sessions can resume project context after compaction or window switch. One brain/ folder, 5 core files (PROJECT/MAP/STATUS/DECISIONS/HANDOFF), and a topic taxonomy.
sprout-labs
Plugin marketplace listing 1 plugin: project-brain.
ralph-wiggum
Implementation of the Ralph Wiggum technique - continuous self-referential AI loops for interactive iterative development. Run Claude in a while-true loop with the same prompt until task completion.
stackmemory
StackMemory integration for Claude Code - context persistence, session handoffs, and memory management.
draft-plugins
Plugin marketplace listing 1 plugin: draft.