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 skills/wolfpackofone/q-agent/push-leannpx skills add WolfpackOfOne/Q-agent --skill push-leangit clone --depth 1 https://github.com/WolfpackOfOne/Q-agentWhat 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.00033 | $0.00954 |
| Opus 5 | $0.00016 | $0.00477 |
| Sonnet 5 | $0.00007 | $0.00191 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
push-lean 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push LEAN Skill
Push a QuantConnect project to its configured Git remote and to QuantConnect Cloud.
Usage
/push-lean [project-name]
Examples:
/push-lean/push-lean MomentumETF/push-lean "My Strategy"
Purpose
Use this skill when the user wants to:
- push or sync a project to QuantConnect Cloud
- deploy the latest changes to QC
- send changes to GitHub and QuantConnect Cloud
This skill is generic and should work for any project under:
~/Documents/Q-agent/MyProjects/<ProjectName>
Project Resolution
Determine the target project in this order:
- If the command includes a project name, use it.
- If the current working directory is inside
MyProjects/<ProjectName>, use that project. - Otherwise, ask the user which project to push.
Preconditions
Before pushing, verify:
- project directory exists under
MyProjects/ - project is a Git repository
- shared LEAN CLI exists at
~/Documents/Q-agent/venv/bin/lean MyProjects/lean.jsonexists
If Git remote configuration is missing, stop and tell the user the project needs to be connected first.
If QuantConnect Cloud push is not configured or fails because the project is not connected, report that clearly and tell the user the project needs to be connected to QuantConnect Cloud before this skill can complete.
Workflow
1. Inspect Current State
From the project directory:
git status --short
git status -sb
git remote -v
git branch --show-current
Review what is about to be pushed before staging or committing.
2. Validate Changed Python Files
If there are changed .py files, run syntax validation before committing.
Prefer validating only changed files. For example:
python -m py_compile main.py
python -m py_compile models/*.py domain/*.py
If validation fails, stop and fix the issue before pushing.
3. Commit Local Changes
If there are uncommitted changes:
- Stage the relevant project files
- Create a clear commit message
- Do not create a commit if there are no 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.
- 2d ago First seen · 164 lines · 33 tokens per session scan A ebaa5f0c98b8
push-lean is a skill published in the GitHub repository WolfpackOfOne/Q-agent (5 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 954 once invoked, about $0.0002 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 skills, from other repositories
kagent-dev
Development guide for kagent's v1alpha3 Harness and AgentTemplate CRDs, AgentInstance gRPC control plane, upstream A2A integration, Substrate runtime provisioning, tests, generation, and PR workflow. Use for any implementation, debugging, review, or CI task in the kagent repository.
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
durable-objects
Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases…
ship-web-games
Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources.
hyperpod-version-checker
Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches…
slo-optimize
Analyzes Grafana SLO timeline trends via gcx and produces data-backed advisory recommendations: objective tuning, alerting sensitivity review, label visibility, or window adjustments. Use when the user wants to analyze SLO performance trends and receive improvement suggestions. Trigger on phrases like "optimize my…