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 nutdnuy/quantcoder-pluginnpx agentmods add plugins/nutdnuy/quantcoder-plugin/marketplacegit clone --depth 1 https://github.com/nutdnuy/quantcoder-pluginGrade A, and why
quantcoder-plugin 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
{
"name": "quantcoder-plugin",
"description": "Marketplace for the QuantCoder Claude Code plugin.",
"owner": {
"name": "nutdnuy",
"url": "https://github.com/nutdnuy"
},
"metadata": {
"description": "Claude Code/Codex Agent-native plugin wrapper around SL-Mar/quantcoder for research-paper to QuantConnect workflows, local QC linting, and optional QuantConnect validation/backtesting through MCP."
},
"plugins": [
{
"name": "quantcoder",
"description": "Turn quantitative research into QuantConnect LEAN algorithm drafts with Claude Code / Codex Agent and verification-first guidance.",
"version": "0.1.0",
"source": "./",
"author": {
"name": "nutdnuy",
"url": "https://github.com/nutdnuy"
}
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 24 lines scan A 89e329bf984e
quantcoder-plugin is a plugin published in the GitHub repository nutdnuy/quantcoder-plugin (1 stars, last pushed 2mo ago), licensed Apache-2.0. 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
brain-paper-to-alpha-plugin
Marketplace for the WQ BRAIN Alpha plugin.
brain-paper-to-alpha-plugin
Agent-native paper-to-alpha workflow plugin for WorldQuant BRAIN research, candidate generation, simulation handoff, repair, and memory logging.
wakeflow
A disciplined control loop for multi-window Claude Code work: a controller window dispatches scoped task packages across a tmux-resident fleet, collects immutable target results, obtains independent Test validation, reviews the evidence, and decides the next step. Explicit on-disk state roots keep the run auditable…
llamaparse-mcp
Unlock document processing and Index v2 retrieval workflows with the LlamaParse Platform MCP.
superb
Personal skill collection. Skills are invoked as superb: . craft turns a vague product idea into a decision-rich CRAFT.md brief — it questions, challenges and records, and deliberately stops short of planning. pipeline takes a settled idea to a finished branch, composing the superpowers skills with a zero-assumpt.
wavedash
Official Wavedash plugins and skills for AI coding agents.