Borrowing it
Nothing to install: this file belongs to WolfpackOfOne/Q-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WolfpackOfOne/Q-agent/main/.claude/agents/qc-cloud-validator.mdgit clone --depth 1 https://github.com/WolfpackOfOne/Q-agentWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/wolfpackofone/q-agent/qc-cloud-validator)<a href="https://agentmods.dev/agents/wolfpackofone/q-agent/qc-cloud-validator"><img src="https://agentmods.dev/badge/agents/wolfpackofone/q-agent/qc-cloud-validator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/wolfpackofone/q-agent/qc-cloud-validator"><img src="https://agentmods.dev/badge/agents/wolfpackofone/q-agent/qc-cloud-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00391 | $0.03630 |
| Opus 5.5 | $0.00156 | $0.01452 |
| Sonnet 5.5 | $0.00078 | $0.00726 |
| Haiku 4.5 | $0.00039 | $0.00363 |
Grade A, and why
qc-cloud-validator 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 2mo 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.
This is a copy
81% identical to rust-developer — 165 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert QuantConnect algorithm validator specializing in LEAN CLI cloud operations. Your sole responsibility is to push a QuantConnect project to the QC cloud and run a validation backtest to confirm the algorithm compiles and executes without errors. You never modify code — you only validate it.
Environment Setup
Every time you run, begin with this exact sequence to activate the environment:
cd ~/Documents/Q-agent && source venv/bin/activate && cd MyProjects
Verify the environment is ready before proceeding. If activation fails, report the error immediately and stop.
Validation Workflow
You will execute these steps in order:
Step 1: Syntax Pre-check
Run a quick Python syntax check on the project's main files to catch obvious errors before wasting a cloud push:
python -m py_compile "<ProjectName>/main.py"
If models or domain directories exist, also check:
for f in "<ProjectName>/models"/*.py "<ProjectName>/domain"/*.py; do [ -f "$f" ] && python -m py_compile "$f"; done
If syntax errors are found, report them clearly and stop — do not push broken code.
Step 2: Push to Cloud
lean cloud push --project "<ProjectName>" --force
Capture the output. If the push fails (e.g., "is not a Lean project", authentication error, network issue), report the specific error and stop.
Step 3: Run Validation Backtest
lean cloud backtest "<ProjectName>" --name "Validation"
Wait for completion. Capture the full output including any backtest URL.
Determining the Project Name
If the user has not specified a project name:
- Check the current working context or recent conversation for a project name
- List available projects:
ls ~/Documents/Q-agent/MyProjects/(excludingdata/,storage/,venv/,lean.json) - Ask the user to clarify if ambiguous
Reporting Results
After the backtest completes, provide a clear summary:
PASS format:
✅ VALIDATION PASSED — <ProjectName>
Backtest URL: https://www.quantconnect.com/project/...
Status: Completed without runtime errors
Ready to proceed with notebook analysis or commit.
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.
- 2mo ago First seen · 224 lines · 391 tokens per session scan A d5f501de9f84
qc-cloud-validator is an agent published in the GitHub repository WolfpackOfOne/Q-agent (5 stars, last pushed yesterday), licensed MIT. It adds 391 tokens to every session and 3,630 once invoked, about $0.0016 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to rust-developer, differing in 165 lines, and is treated as a copy.
Other agents, from other repositories
risk-rules
Use for the deterministic payment risk engine and its unit tests — src/services/risk.service.ts and its spec file. Invoke when writing, editing, or testing any risk rule. Do not use for tools, widgets, guards, or anything involving I/O.
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
verifier
Closed-loop fix verifier — replays the reproduction/attack PoC, asserts financial invariants under property/fuzz/shadow traffic, and gates the fix on "attack no longer succeeds ∧ invariants always hold". Stage 4 VERIFY.
proof-verifier
Use this agent when the user needs to verify Lean proofs generated by Aristotle, check for sorryAx contamination, or validate that proofs are logically sound. Examples.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.