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.
npx agentmods add commands/nutdnuy/quantcoder-plugin/quantcoder-validategit clone --depth 1 https://github.com/nutdnuy/quantcoder-pluginWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00012 | $0.00173 |
| Opus 5 | $0.00006 | $0.00086 |
| Sonnet 5 | $0.00002 | $0.00035 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
quantcoder-validate 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
Validate a QuantConnect Python algorithm.
For local static linting only, run the supplied file path with --local-only
if the user did not already include it:
cd "${CLAUDE_PLUGIN_ROOT}" && uv run quantcoder validate <file_path> --local-only
For QuantConnect compile validation, omit --local-only and ensure
QUANTCONNECT_API_KEY and QUANTCONNECT_USER_ID are set:
cd "${CLAUDE_PLUGIN_ROOT}" && uv run quantcoder validate <file_path>
Report compile errors separately from strategy/research concerns.
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 · 12 tokens per session scan A d15f3c1fb867
quantcoder-validate is a command published in the GitHub repository nutdnuy/quantcoder-plugin (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 173 once invoked, about $0.0001 per session on Opus 5. 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 commands, from other repositories
brain-generate-candidates
Generate a small, source-grounded BRAIN alpha candidate batch.
brain-init-run
Create a local BRAIN paper-to-alpha research run folder.
brain-setup
Check local WQ BRAIN alpha artifact utilities.
brain-validate-run
Validate a local BRAIN alpha research run folder.
brain-intake
Convert a paper, report, idea, alpha expression, or BRAIN result into a research card.
brain-repair
Diagnose failed BRAIN alpha results and propose a repair batch.