Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sillyDaibo/reasflow-devnpx agentmods add skills/sillydaibo/reasflow-dev/domain-knowledge-cardsWrote 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/sillydaibo/reasflow-dev/domain-knowledge-cards)<a href="https://agentmods.dev/skills/sillydaibo/reasflow-dev/domain-knowledge-cards"><img src="https://agentmods.dev/badge/skills/sillydaibo/reasflow-dev/domain-knowledge-cards.svg" alt="Measured on agentmods" 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.00029 | $0.00443 |
| Opus 5 | $0.00015 | $0.00221 |
| Sonnet 5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
domain-knowledge-cards 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 7d 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.
What it actually says
Installed Root
Resolve the installed reasflow-dev skills root before running packaged scripts:
REASFLOW_SKILLS_ROOT="${REASFLOW_SKILLS_ROOT:-}"
if [ -z "$REASFLOW_SKILLS_ROOT" ]; then
if [ -d ./.agents/skills ]; then
REASFLOW_SKILLS_ROOT="$(pwd)/.agents/skills"
elif [ -d "$HOME/.agents/skills" ]; then
REASFLOW_SKILLS_ROOT="$HOME/.agents/skills"
else
echo "reasflow-dev skills not found in ./.agents/skills or $HOME/.agents/skills" >&2
exit 1
fi
fi
Domain Knowledge Cards
Overview
Treat domain knowledge as a local artifact set, not a vague memory. Search existing cards first, then generate new workspace-local cards from arXiv only for papers that materially affect method or experiment decisions.
Helper Scripts
SKILL_ROOT="$REASFLOW_SKILLS_ROOT/domain-knowledge-cards"python "$SKILL_ROOT/scripts/search-domain-knowledge.py" --root Alg_Exp/src/domain_knowledge --query "variance reduced decentralized optimization" --top-k 5python "$SKILL_ROOT/scripts/create-knowledge-card-from-arxiv.py" --query "decentralized variance reduction" --max-results 3 --output-dir Alg_Exp/src/domain_knowledge
Workflow
- Search existing workspace-local cards before creating new ones.
- Generate cards only for papers that inform the active algorithm or experiment question.
- Keep generated YAML under
src/domain_knowledge/or another explicit workspace-local card directory. - Record which cards were reused versus newly generated from arXiv.
Deliverables
- ranked local card shortlist with exact file paths
- generated YAML cards with title, method, evidence, baselines, and limitations
- note on which experiment or design choice each card informs
What ships with it
2 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.
- 7d ago First seen · 44 lines · 29 tokens per session scan A abcd958dc7e0
domain-knowledge-cards is a skill published in the GitHub repository sillyDaibo/reasflow-dev (2 stars, last pushed 11d ago), licensed MIT. It adds 29 tokens to every session and 443 once invoked, about $0.0001 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
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…