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/opendcai/dataflow-webui/core_textnpx skills add OpenDCAI/DataFlow-WebUI --skill core_textgit clone --depth 1 https://github.com/OpenDCAI/DataFlow-WebUIWhat 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.00068 | $0.00664 |
| Opus 5 | $0.00034 | $0.00332 |
| Sonnet 5 | $0.00014 | $0.00133 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
core_text 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
core_text operator reference
Per-operator API documentation for DataFlow's core_text family. Consult it when
you need an operator's exact constructor and run() signature, its real
row-processing behaviour, or the mistakes that break it.
Do not invoke this as a skill. There is no workflow here. The
generating-dataflow-pipeline skill reads these files when it needs an operator
beyond its six core primitives.
Layout
core_text/<category>/<operator>/
├── SKILL.md English reference: constructor, run(), execution logic,
│ mandatory rules, return-value semantics
├── SKILL_zh.md Chinese translation
└── examples/
├── good.md Best-practice pipeline usage
└── bad.md Common mistakes and how they fail
What is documented
| Category | Path | Operators |
|---|---|---|
| Generate | generate/ |
PromptedGenerator, FormatStrPromptedGenerator, Text2MultiHopQAGenerator, BenchAnswerGenerator, ChunkedPromptedGenerator, EmbeddingGenerator, RandomDomainKnowledgeRowGenerator, RetrievalGenerator |
| Filter | filter/ |
GeneralFilter, KCenterGreedyFilter, PromptedFilter |
| Refine | refine/ |
PandasOperator, PromptedRefiner |
| Eval | eval/ |
BenchDatasetEvaluator, BenchDatasetEvaluatorQuestion, PromptedEvaluator, Text2QASampleEvaluator, UnifiedBenchDatasetEvaluator |
How to use it
- Find the operator's directory under its category.
- Read its
SKILL.mdfor the authoritative signature. - Check that operator's
bad.mdexample before writing code — it documents the failure modes that come up most often.
Accuracy and scope
These are static reference docs, aligned to a specific DataFlow version
(recorded in VERSION.md in this directory). They are not a live query.
When an MCP server is available, get_operator_detail_by_name is authoritative:
it reflects the operators actually installed. Prefer it, and treat a
disagreement with these files as this reference being out of date.
What ships with it
60 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.
- eval/bench-dataset-evaluator-question/examples/bad.md 853 B
- eval/bench-dataset-evaluator-question/examples/good.md 2.8 KB
- eval/bench-dataset-evaluator-question/SKILL_zh.md 6.3 KB
- eval/bench-dataset-evaluator-question/SKILL.md 6.6 KB
- eval/bench-dataset-evaluator/examples/bad.md 836 B
- eval/bench-dataset-evaluator/examples/good.md 4.9 KB
- eval/bench-dataset-evaluator/SKILL_zh.md 4.9 KB
- eval/bench-dataset-evaluator/SKILL.md 6.7 KB
- eval/prompted-evaluator/examples/bad.md 821 B
- eval/prompted-evaluator/examples/good.md 2.3 KB
- eval/prompted-evaluator/SKILL_zh.md 2.8 KB
- eval/prompted-evaluator/SKILL.md 2.9 KB
- eval/text2qa-sample-evaluator/examples/bad.md 1.2 KB
- eval/text2qa-sample-evaluator/examples/good.md 2.3 KB
- eval/text2qa-sample-evaluator/SKILL_zh.md 3.8 KB
- eval/text2qa-sample-evaluator/SKILL.md 3.8 KB
- eval/unified-bench-dataset-evaluator/examples/bad.md 1.4 KB
- eval/unified-bench-dataset-evaluator/examples/good.md 2.5 KB
- eval/unified-bench-dataset-evaluator/SKILL_zh.md 6.2 KB
- eval/unified-bench-dataset-evaluator/SKILL.md 6.4 KB
- filter/general-filter/examples/bad.md 648 B
- filter/general-filter/examples/good.md 1.9 KB
- filter/general-filter/SKILL_zh.md 3.3 KB
- filter/general-filter/SKILL.md 3.6 KB
- filter/kcentergreedy-filter/examples/bad.md 724 B
- filter/kcentergreedy-filter/examples/good.md 2.3 KB
- filter/kcentergreedy-filter/SKILL_zh.md 5.1 KB
- filter/kcentergreedy-filter/SKILL.md 5.3 KB
- filter/prompted-filter/examples/bad.md 853 B
- filter/prompted-filter/examples/good.md 2.5 KB
- filter/prompted-filter/SKILL_zh.md 4.9 KB
- filter/prompted-filter/SKILL.md 5.4 KB
- generate/bench-answer-generator/examples/bad.md 1.2 KB
- generate/bench-answer-generator/examples/good.md 2.9 KB
- generate/bench-answer-generator/SKILL_zh.md 7.0 KB
- generate/bench-answer-generator/SKILL.md 7.3 KB
- generate/chunked-prompted-generator/examples/bad.md 659 B
- generate/chunked-prompted-generator/examples/good.md 3.3 KB
- generate/chunked-prompted-generator/SKILL_zh.md 4.4 KB
- generate/chunked-prompted-generator/SKILL.md 4.6 KB
- generate/embedding-generator/examples/bad.md 731 B
- generate/embedding-generator/examples/good.md 2.8 KB
- generate/embedding-generator/SKILL_zh.md 5.3 KB
- generate/embedding-generator/SKILL.md 5.4 KB
- generate/format-str-prompted-generator/examples/bad.md 1.4 KB
- generate/format-str-prompted-generator/examples/good.md 3.4 KB
- generate/format-str-prompted-generator/SKILL_zh.md 5.2 KB
- generate/format-str-prompted-generator/SKILL.md 5.4 KB
- generate/prompted-generator/examples/good.md 1.8 KB
- generate/prompted-generator/SKILL_zh.md 3.2 KB
- generate/prompted-generator/SKILL.md 3.4 KB
- generate/random-domain-knowledge-row-generator/examples/bad.md 1.0 KB
- generate/random-domain-knowledge-row-generator/examples/good.md 3.0 KB
- generate/random-domain-knowledge-row-generator/SKILL_zh.md 4.4 KB
- generate/random-domain-knowledge-row-generator/SKILL.md 4.7 KB
- generate/retrieval-generator/examples/bad.md 1.5 KB
- generate/retrieval-generator/examples/good.md 2.7 KB
- generate/retrieval-generator/SKILL_zh.md 4.1 KB
- generate/retrieval-generator/SKILL.md 4.1 KB
- generate/text2multihopqa-generator/examples/bad.md 1.1 KB
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 · 64 lines · 68 tokens per session scan A 7d1e09b10673
core_text is a skill published in the GitHub repository OpenDCAI/DataFlow-WebUI (224 stars, last pushed 7d ago), licensed Apache-2.0. It adds 68 tokens to every session and 664 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…