Q-agent: Agent for Claude Code

.claude/agents/qc-cloud-validator.md

qc-cloud-validator is an agent for Claude Code from WolfpackOfOne/Q-agent. It costs 391 tokens per session (3,630 once invoked), scanned A, a copy of rust-developer, MIT.

A validator for QuantConnect trading algorithms that checks Python syntax, uploads the project to QuantConnect's cloud, and runs a validation backtest. QuantConnect is a service for writing and testing automated trading strategies.

In plain words
What is it for?
Use it after significant algorithm changes to perform syntax checks, push the project to QuantConnect, and run a validation backtest without modifying the code.
Why use it?
It catches basic code errors before a cloud run and confirms that the algorithm compiles and executes without errors in the target environment.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md.

This is WolfpackOfOne/Q-agent's own configuration. It tells Claude Code how to work on Q-agent itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Q-agent configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/WolfpackOfOne/Q-agent/main/.claude/agents/qc-cloud-validator.md
Clone the repo
git clone --depth 1 https://github.com/WolfpackOfOne/Q-agent

Made for: Claude Code.

Wrote 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.

agentmods badge for qc-cloud-validator

README.md
[![agentmods](https://agentmods.dev/badge/agents/wolfpackofone/q-agent/qc-cloud-validator/github.svg)](https://agentmods.dev/agents/wolfpackofone/q-agent/qc-cloud-validator)
Your own site
<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.

agentmods 80×15 button for qc-cloud-validator

Your own site · 80×15
<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>
Per session 391 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,630 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 81% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2mo ago against content hash d5f501de9f84, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

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.

.claude/agents/qc-cloud-validator.md · 224 lines

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:

  1. Check the current working context or recent conversation for a project name
  2. List available projects: ls ~/Documents/Q-agent/MyProjects/ (excluding data/, storage/, venv/, lean.json)
  3. 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.

Read the full file on GitHub · 224 lines

Changes

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.

  1. 2mo ago First seen · 224 lines · 391 tokens per session scan A d5f501de9f84

Subscribe to this mod's changes

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.

Related

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.

nitrocloudofficial/nitrostack · 55 tokens

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…

avelikiy/great_cto · 83 tokens

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.

yao-beyond/debug-hunter · 51 tokens

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.

afhverjuekki/claude-code-aristotle-plugin · 35 tokens

gsd-integration-checker

Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.

swisstruthorg/swiss-truth-mcp · 31 tokens

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.

microsoft/playwright · 151 tokens