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 skills add wentorai/research-plugins --skill prompt-engineering-researchgit 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/prompt-engineering-research)<a href="https://agentmods.dev/skills/wentorai/research-plugins/prompt-engineering-research"><img src="https://agentmods.dev/badge/skills/wentorai/research-plugins/prompt-engineering-research/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/wentorai/research-plugins/prompt-engineering-research"><img src="https://agentmods.dev/badge/skills/wentorai/research-plugins/prompt-engineering-research.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.00019 | $0.01699 |
| Opus 5 | $0.00010 | $0.00849 |
| Sonnet 5 | $0.00004 | $0.00340 |
| Haiku 4.5 | $0.00002 | $0.00170 |
Grade A, and why
prompt-engineering-research 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 6d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Engineering for Research
A skill for applying systematic prompt engineering techniques in academic research contexts. Covers prompt design patterns, evaluation methodologies, and practical workflows for using large language models (LLMs) as research tools.
Prompt Design Patterns
Core Prompting Strategies
| Strategy | Description | Best For | Reliability |
|---|---|---|---|
| Zero-shot | Direct instruction, no examples | Simple, well-defined tasks | Moderate |
| Few-shot | Include 2-5 examples in prompt | Pattern matching, formatting | High |
| Chain-of-thought | "Think step by step" | Reasoning, math, analysis | High |
| Role prompting | "You are an expert in..." | Domain-specific tasks | Moderate |
| Structured output | Request JSON/YAML/table format | Data extraction | High |
| Self-consistency | Sample multiple times, majority vote | Fact-checking, reasoning | Very high |
Research-Specific Prompt Templates
def create_research_prompt(task_type: str, context: dict) -> str:
"""
Generate a structured prompt for common research tasks.
Args:
task_type: One of 'literature_summary', 'methodology_critique',
'code_review', 'data_interpretation', 'writing_feedback'
context: Dict with task-specific context
"""
templates = {
'literature_summary': """
You are an academic researcher specializing in {domain}.
Summarize the following paper excerpt, focusing on:
1. The research question and its significance
2. The methodology used
3. Key findings and their implications
4. Limitations acknowledged by the authors
5. How this work relates to {related_topic}
Paper excerpt:
{text}
Provide a structured summary in 200-300 words. Distinguish clearly
between what the authors claim and what the evidence supports.
""",
'methodology_critique': """
You are a methods expert reviewing a research design.
Evaluate the following methodology description:
{text}
Assess the following:
1. Internal validity: Are there confounding variables not controlled?
2. External validity: How generalizable are the findings?
3. Statistical approach: Is the analysis appropriate for the data?
4. Sample: Is the sample size adequate? Any selection bias?
5. Reproducibility: Could another researcher replicate this?
For each concern, rate severity (minor/moderate/major) and suggest
a specific improvement.
""",
'data_interpretation': """
You are a statistical consultant helping interpret results.
Given these results:
{results}
Context: {context_description}
Provide:
1. Plain-language interpretation of each result
2. Effect size interpretation (is it practically significant?)
3. Potential alternative explanations
4. Caveats the authors should mention
5. Suggested follow-up analyses
Be precise about what the data does and does not support.
Do not overstate findings.
"""
}
template = templates.get(task_type, templates['literature_summary'])
return template.format(**context)
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.
- 6d ago First seen · 234 lines · 19 tokens per session scan A f4863b82adc2
prompt-engineering-research is a skill published in the GitHub repository wentorai/research-plugins (291 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 1,699 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-09-03.
Other skills, from other repositories
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
prompt-optimization
Improve a prompt on the evaluations workbench through a measured loop. Score the baseline first, then duplicate the target column, form a hypothesis from failing rows, edit the copy's prompt draft, run, compare pass rate and cost, and repeat until the numbers hold. Use when the user asks to optimize or improve a…
enhance-prompt
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
prompt-engineer
Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot…
seedance-vocab-en
This skill should be used when an English Seedance 2.0 prompt needs clearer production wording, less generic prose, or precise vocabulary for camera, lighting, motion, VFX, audio, and constraints. Route blocked prompts through seedance-filter for context and boundary review.
ideogram4
Prompting patterns for Ideogram 4 text-to-image — best-in-class in-image text rendering and exact color/layout control via structured JSON captions. Use when generating images that need legible on-image text (title cards, thumbnails, logos, signage, CTAs), precise brand colors, or controlled spatial layout. Triggers…