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 X-School-Academy/skill-pilot --skill deep-researchgit clone --depth 1 https://github.com/X-School-Academy/skill-pilotWrote 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/x-school-academy/skill-pilot/deep-research)<a href="https://agentmods.dev/skills/x-school-academy/skill-pilot/deep-research"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/deep-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/x-school-academy/skill-pilot/deep-research"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/deep-research.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.00037 | $0.00505 |
| Opus 5.5 | $0.00015 | $0.00202 |
| Sonnet 5.5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
deep-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 16d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Builder - Deep Research
Perform a structured research pass from a research requirement file.
When to Use This Skill
- The user wants a deep research result from
workspace/research/{topic}/requirements.md - The user provides any requirement, task, or instruction file and wants the result written beside it
- The work requires gathering, organizing, and synthesizing research findings
- The output should be written back into the topic workspace
Your Roles in This Skill
- Research Analyst: Gather and synthesize relevant findings
- Technical Writer: Turn findings into a clear output document
Role Communication
As an expert in your assigned roles, you must announce your actions before performing them using the following format:
As a {Role} [and {Role}, ...], I will {action description}
This communication pattern ensures transparency and allows for human-in-the-loop oversight at key decision points.
Instructions
Step 1: Read the Requirement
Read the referenced research requirements.md carefully and identify the scope, research questions, and expected deliverable.
If the user provides a requirement, task, or instruction file path, use that file's parent folder as the output folder unless the user explicitly provides another output path.
Step 2: Perform the Research
Gather and synthesize the most relevant information for the requested topic.
Step 3: Write the Result
Save the result inside the same folder as the instruction file when one exists. Markdown is the default source format.
When the result benefits from visual explanation, also create:
index.html
The HTML report should be a polished visual report, not just raw Markdown. Use Mermaid diagrams, tables, sections, and navigation when useful. Put any Mermaid source files, images, or supporting assets in the same folder or a child folder so the report works as a static page rooted at that folder. If Mermaid diagrams are included, also save their .mmd source files where practical.
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.
- 16d ago First seen · 59 lines · 37 tokens per session scan A 6282ba7dbf03
deep-research is a skill published in the GitHub repository X-School-Academy/skill-pilot (20 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 505 once invoked, about $0.0001 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-10-02.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.