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/wentorai/research-plugins/data-cog-guidenpx skills add wentorai/research-plugins --skill data-cog-guidegit clone --depth 1 https://github.com/wentorai/research-pluginsWrote 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/wentorai/research-plugins/data-cog-guide)<a href="https://agentmods.dev/skills/wentorai/research-plugins/data-cog-guide"><img src="https://agentmods.dev/badge/skills/wentorai/research-plugins/data-cog-guide.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 | $0.00016 | $0.01605 |
| Opus 5 | $0.00008 | $0.00803 |
| Sonnet 5 | $0.00003 | $0.00321 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade A, and why
data-cog-guide 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 4d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Cog Guide
An intelligent data analysis assistant that accepts messy, poorly documented CSV files and automatically infers structure, cleans anomalies, and produces deep analytical reports with minimal user prompting. Designed for researchers who need quick insights from unfamiliar or inherited datasets without spending hours on manual data preparation.
Overview
Researchers frequently receive datasets from collaborators, public repositories, or legacy systems that lack documentation, use inconsistent formatting, and contain mixed data quality. Traditional analysis requires significant upfront effort to understand and prepare such data. Data Cog automates this process by applying heuristic inference, pattern recognition, and iterative cleaning to produce analysis-ready data along with a comprehensive profile report.
The skill implements a "zero-configuration" philosophy: provide the CSV file path and an optional research question, and it handles encoding detection, delimiter inference, type casting, missingness assessment, and initial exploratory statistics automatically.
Automated Ingestion Pipeline
Smart Loading
import pandas as pd
import chardet
import io
def smart_load_csv(filepath: str) -> tuple:
"""
Intelligently load a CSV file, auto-detecting encoding,
delimiter, header row, and comment lines.
"""
# Step 1: Detect encoding
with open(filepath, 'rb') as f:
raw = f.read(100000)
encoding = chardet.detect(raw)['encoding']
# Step 2: Detect delimiter
import csv
with open(filepath, 'r', encoding=encoding, errors='replace') as f:
sample = f.read(8192)
sniffer = csv.Sniffer()
try:
dialect = sniffer.sniff(sample)
delimiter = dialect.delimiter
except csv.Error:
delimiter = ','
# Step 3: Detect header row (skip comment lines)
skip_rows = 0
with open(filepath, 'r', encoding=encoding, errors='replace') as f:
for line in f:
if line.startswith('#') or line.startswith('//') or line.strip() == '':
skip_rows += 1
else:
break
# Step 4: Load with inferred parameters
df = pd.read_csv(
filepath, encoding=encoding, delimiter=delimiter,
skiprows=skip_rows, low_memory=False
)
metadata = {
'encoding': encoding,
'delimiter': repr(delimiter),
'skipped_rows': skip_rows,
'shape': df.shape
}
return df, metadata
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.
- 4d ago First seen · 179 lines · 16 tokens per session scan A b09e353e0185
data-cog-guide is a skill published in the GitHub repository wentorai/research-plugins (285 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 1,605 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-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…