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/survey-data-processingnpx skills add wentorai/research-plugins --skill survey-data-processinggit clone --depth 1 https://github.com/wentorai/research-pluginsWhat 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.02223 |
| Opus 5 | $0.00008 | $0.01111 |
| Sonnet 5 | $0.00003 | $0.00445 |
| Haiku 4.5 | $0.00002 | $0.00222 |
Grade A, and why
survey-data-processing 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Survey Data Processing
A skill for cleaning, recoding, and preparing survey response data for statistical analysis. Covers handling common survey data issues such as incomplete responses, attention check failures, reverse-coded items, scale construction, open-ended response coding, and export to analysis-ready formats compatible with SPSS, Stata, and R.
Survey Data Quality Assessment
Initial Inspection Workflow
Survey data from platforms like Qualtrics, SurveyMonkey, REDCap, and Google Forms each have their own export formats and quirks. The first step is always standardization.
import pandas as pd
import numpy as np
def assess_survey_quality(df, duration_col="duration_seconds",
min_duration=60):
"""
Generate a survey data quality report.
Checks:
- Completion rates per question
- Response duration (speeders and slow responders)
- Straight-line responding patterns
- Attention check failures
"""
report = {}
# Overall completion
total_respondents = len(df)
complete = df.dropna(thresh=int(len(df.columns) * 0.8))
report["total_responses"] = total_respondents
report["substantially_complete"] = len(complete)
report["completion_rate"] = f"{len(complete)/total_respondents*100:.1f}%"
# Duration analysis
if duration_col in df.columns:
durations = df[duration_col].dropna()
report["median_duration_seconds"] = durations.median()
report["speeders"] = (durations < min_duration).sum()
report["speeder_pct"] = f"{(durations < min_duration).mean()*100:.1f}%"
# Missing data per question
missing_by_col = df.isna().sum().sort_values(ascending=False)
report["most_skipped_questions"] = missing_by_col.head(10).to_dict()
return report
Identifying Low-Quality Responses
def detect_straightlining(df, likert_columns, threshold=0.9):
"""
Detect respondents who select the same answer for nearly
all Likert-scale questions (straight-line responding).
A respondent is flagged if the proportion of their most
common response exceeds the threshold.
"""
flagged = []
for idx, row in df[likert_columns].iterrows():
responses = row.dropna()
if len(responses) == 0:
continue
most_common_pct = responses.value_counts().iloc[0] / len(responses)
if most_common_pct >= threshold:
flagged.append(idx)
return flagged
def check_attention_items(df, attention_checks):
"""
Validate attention check (trap) questions.
Args:
attention_checks: dict of {column_name: correct_answer}
Example: {"q15_attention": 4, "q32_trap": "strongly agree"}
"""
failed = pd.Series(False, index=df.index)
for col, correct in attention_checks.items():
failed = failed | (df[col] != correct)
return df.index[failed].tolist()
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 · 299 lines · 16 tokens per session scan A f3a47d1d75d4
survey-data-processing is a skill published in the GitHub repository wentorai/research-plugins (284 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 2,223 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.