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/abilenduke/copilot-developer/research-briefnpx skills add ABilenduke/copilot-developer --skill research-briefgit clone --depth 1 https://github.com/ABilenduke/copilot-developerWhat 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.00047 | $0.02488 |
| Opus 5 | $0.00023 | $0.01244 |
| Sonnet 5 | $0.00009 | $0.00498 |
| Haiku 4.5 | $0.00005 | $0.00249 |
Grade A, and why
research-brief 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Brief Generator
HARD RULES
These rules are absolute. No exceptions.
Rule 1: NEVER do research yourself
You are a context packager, not a researcher. Your job is to scan the codebase, gather facts, and frame questions. You do NOT answer the research questions, suggest architectures, or recommend packages. The external AI research tool does that. You provide the raw material.
Rule 2: NEVER fabricate codebase details
Every code excerpt, version number, file path, and pattern description in the brief MUST come from actually reading the codebase. If you can't find something, say it doesn't exist. Never invent model relationships, guess at config values, or assume a file's contents.
Rule 3: Structural contracts inline, behavioral implementation summarized
This is the core content rule for the brief:
Inline as actual code (structural contracts):
- Model relationships, casts, traits (10-20 lines per model)
- Migration schema (column names, types, indexes)
- Pattern exemplar key files (service class, job chain, controller)
- Route definitions for the relevant area
- TypeScript type definitions and interfaces
Summarize, don't inline (behavioral implementation):
- Controller method bodies — summarize the flow
- Vue component templates — describe the structure
- Config files — note the relevant settings
- Test files — note the patterns used
Rule 4: Constraints go FIRST in the brief
The brief is read top-to-bottom by the research tool. Constraints and non-negotiables must appear before research objectives so the AI internalizes your boundaries before forming answers.
Purpose
This skill bridges Claude Code and external AI deep research tools (Gemini Deep Research, Perplexity, ChatGPT, etc.). Claude does what it's good at — reading your codebase, understanding your patterns — and produces a self-contained briefing document. The research tool does what it's good at — deep web research — but grounded in your actual stack, architecture, and constraints instead of giving generic advice.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 218 lines · 47 tokens per session scan A 2bea04442e5e
research-brief is a skill published in the GitHub repository ABilenduke/copilot-developer (4 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 2,488 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…