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/idea-researchgit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginsGrade A, and why
idea-research 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": "idea-research",
"version": "1.0.0",
"description": "Comprehensive business research, market analysis, competitor intelligence, and idea validation for Claude Code",
"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": [
"research",
"market-analysis",
"competitor-intelligence",
"idea-validation",
"business-strategy",
"TAM-SAM-SOM"
],
"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 · 22 lines scan A d0be5df06abc
idea-research 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.
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.
coaltipple
CoalTipple — model/effort router for Claude Code. Delegates a task you CAN do but is large+cheap DOWN to a lower tier to save tokens; escalates a task beyond the current tier UP for quality — up to Fable 5, the top rung (a consent-gated, real-money spawn). Two-knob routing (tier × effort, effort-before-tier), an alias.
sipcode
Token-economy observatory for Claude Code: forensic per-session audit, A/B savings verifier, reproducible benchmark, and cost prediction — directly in Claude chat. Auto-installs via npx on first use; no separate npm install required.