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/llmquant/quant-mind/quantmind-devnpx skills add LLMQuant/quant-mind --skill quantmind-devgit clone --depth 1 https://github.com/LLMQuant/quant-mindWhat 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.00090 | $0.00812 |
| Opus 5 | $0.00045 | $0.00406 |
| Sonnet 5 | $0.00018 | $0.00162 |
| Haiku 4.5 | $0.00009 | $0.00081 |
Grade A, and why
quantmind-dev 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QuantMind Dev
Development workflow for contributing to the QuantMind codebase.
Start Here
- Use the repository
contexts/README.mdto select the development context for this contribution. - Read the repository root
AGENTS.mdorCLAUDE.mdfor the stable architecture constraints and the module map. - Read
docs/README.mdwhen the task adds, changes, or uses a public operation or public-network source. - When creating, updating, or triaging an issue or pull request, use the
canonical repository label guidance in
contexts/dev/labels.md. - Before writing or editing any GitHub body, follow the canonical
GitHub writing style in
contexts/dev/github-writing.md, including its no-hard-wrap rule. - Pick exactly one workflow reference below; do not load the others.
Select Workflow
- Setting up as a contributor (environment, hooks, first verify) →
references/setup.md - Filing an issue for a bug or a missing capability →
references/setup.md("File an Issue" section) - Committing staged work →
references/commit.md - Opening or updating a pull request →
references/pull-request.md - Implementing or refactoring anything under
quantmind/→references/develop-components.md(read it before writing code) - Adding or editing a page under
contexts/→references/write-contexts.md
A feature task usually chains all three: develop → commit → pull request.
Rules
bash scripts/verify.shis the deterministic required verification. Run it before every push and before marking a PR ready. The required.github/workflows/ci.ymlworkflow runs the same harness.- Public-network integrations have separate bounded smoke tests.
.github/workflows/e2e.ymlowns their scheduled, manual, and path-filtered component jobs. Run every applicable test listed indocs/README.mdwhen changing that component and before publishing. External service availability must not block unrelated changes. - Keep
docs/README.mdas the single catalog of component smoke-test commands. A new live component adds a component-specificscripts/verify_<component>_e2e.py, a named job in the existinge2e.yml, precise PR path coverage, and one catalog row. When multiple live jobs exist, use GitHub-native per-job change detection so only affected jobs run. Do not add a separate workflow, generic E2E runner or registry, or base E2E class. - Never bypass pre-commit / pre-push hooks (
--no-verify) unless the user explicitly authorizes it. - New features ship with a unit test and a focused example (see
references/develop-components.md). - This skill is mirrored under
.agents/skills/quantmind-dev/and.claude/skills/quantmind-dev/; the copies are identical. When changing the skill, update both in the same change.
What ships with it
6 files beside SKILL.md 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.
- 2d ago First seen · 69 lines · 90 tokens per session scan A af3eb1ca5f5f
quantmind-dev is a skill published in the GitHub repository LLMQuant/quant-mind (2,763 stars, last pushed 17d ago), licensed MIT. It adds 90 tokens to every session and 812 once invoked, about $0.0005 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-30.
Other skills, from other repositories
ai-news-daily
端到端 pipeline —— 抓 X/知乎/Bilibili AI 相关热门 → 整理成 wiki → 推送飞书日报.
data-engineer
Builds data infrastructure — ETL/ELT pipelines, data warehousing, stream processing, data quality, orchestration (Airflow/Dagster), and analytics engineering (dbt). Use when the user asks to build data pipelines, set up ETL/ELT workflows, design a data warehouse, configure stream processing, or implement analytics…
data-engineering
Data Engineering Review: Reviews data pipelines, ETL/ELT processes, data quality frameworks, data contracts, and data platform architecture. Covers batch and streaming pipelines, data lakes/warehouses, dbt, Airflow, Spark, data governance, and data observability. Use when the user mentions data pipeline, ETL, ELT…
data-pipeline
Data pipeline expert for ETL, Apache Spark, Airflow, dbt, and data quality.
magazine-web-ppt
For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query "annual-marketing-plan", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.
html-ppt-zhangzara-coral
OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.