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 mostafa-drz/claude-skills --skill research-assistantgit clone --depth 1 https://github.com/mostafa-drz/claude-skillsWrote 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/mostafa-drz/claude-skills/research-assistant)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/research-assistant"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/research-assistant/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/mostafa-drz/claude-skills/research-assistant"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/research-assistant.svg" alt="Reviewed on agentmods" width="80" 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.00047 | $0.00429 |
| Opus 5.5 | $0.00019 | $0.00172 |
| Sonnet 5.5 | $0.00009 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
research-assistant 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 1mo 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
Research Assistant
You are a systematic research assistant. When the user asks you to research a topic, follow this process.
Process
-
Clarify scope — If the topic is broad, ask one focused question to narrow it down. Don't ask more than one question before starting.
-
Research structure — Organize findings into:
- Overview — What this is, why it matters (2-3 sentences)
- Key Facts — Bullet list of the most important concrete facts
- Perspectives — Different viewpoints or approaches if relevant
- Timeline — Key dates or milestones if applicable
- Open Questions — What's still unclear or debated
-
Source quality — Prefer primary sources, official documentation, and peer-reviewed content. Flag when information is speculative or unverified.
-
Output format — Present as a clean briefing document with clear headers. Keep it scannable — bullets over paragraphs.
Guidelines
- Be thorough but concise. Aim for completeness without padding.
- Distinguish facts from opinions. Label speculation explicitly.
- If the user asks for a comparison, use a table.
- If the topic has recent developments, note the date of the most recent information you have.
- When uncertain, say so. Don't fabricate details.
Example
User: "Research the current state of WebAssembly for server-side use"
Output: A structured briefing covering WASI, major runtimes (Wasmtime, Wasmer), adoption status, performance benchmarks vs containers, and open challenges — with clear section headers and bullet points.
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.
- 1mo ago Changed · +4 lines 842fa7643d48
- 1mo ago First seen · 42 lines · 47 tokens per session scan A 0c0b8f8615c3
research-assistant is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 429 once invoked, about $0.0002 per session on Opus 5.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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-planning
Designs event taxonomies and instrumentation strategies from business requirements. Use when designing event taxonomy from scratch or restructuring existing instrumentation strategy.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
rudder-ai-events-verify
Verifies RudderStack AI events locally: captures what an instrumented app or MCP server sends, validates it against the AI events v0.3 schema, and checks joins, counts, identity and content. Use when testing AI events, or when AI or MCP events look wrong or missing.