QuantMind is a knowledge extraction and retrieval framework for quantitative finance that turns papers, news, and filings into structured, cited, time-aware financial knowledge. It supports quantitative researchers and downstream systems that need reliable financial information for retrieval and reasoning. Its catalogue add-ons help coding agents build and verify QuantMind workflows inside the repository.
Borrowing it
Nothing to install: this file belongs to LLMQuant/quant-mind. 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/LLMQuant/quant-mind/master/.agents/skills/quantmind-dev/SKILL.mdgit clone --depth 1 https://github.com/LLMQuant/quant-mindWrote 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/skills/llmquant/quant-mind/quantmind-dev)<a href="https://agentmods.dev/skills/llmquant/quant-mind/quantmind-dev"><img src="https://agentmods.dev/badge/skills/llmquant/quant-mind/quantmind-dev/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/skills/llmquant/quant-mind/quantmind-dev"><img src="https://agentmods.dev/badge/skills/llmquant/quant-mind/quantmind-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00090 | $0.00812 |
| Opus 5.5 | $0.00036 | $0.00325 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (3,115 stars, last pushed 2mo ago), licensed MIT. It adds 90 tokens to every session and 812 once invoked, about $0.0004 per session on Opus 5.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
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.
ci-commit
Only use when the user explicitly invokes this skill by name.
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.