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 OutThisLife/brooklyn-skills --skill researchgit clone --depth 1 https://github.com/OutThisLife/brooklyn-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/outthislife/brooklyn-skills/research)<a href="https://agentmods.dev/skills/outthislife/brooklyn-skills/research"><img src="https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/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/outthislife/brooklyn-skills/research"><img src="https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/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.00067 | $0.00968 |
| Opus 5.5 | $0.00027 | $0.00387 |
| Sonnet 5.5 | $0.00013 | $0.00194 |
| Haiku 4.5 | $0.00007 | $0.00097 |
Grade A, and why
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 2mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research
Two halves, in this order: the documents of record for this project, then prior art outside it. Answering from memory and calling it research is the thing this skill is here to stop.
Match the shape of the ask:
- A question ("is this possible", "are we doing this right", "don't touch
code"): look it up, report, stop. No edits until told to go (→
audit-only). - Part of the work ("research and fix", "sleuth GitHub and iterate until it's right"): research inside the loop. Look, apply, re-check, and say what each pass was based on — don't halt the loop to file a report.
Pick a depth and say it
| Depth | For | Shape |
|---|---|---|
| quick | one fact, one API, one flag | a source or two, answer in a paragraph |
| medium | "how do people do this", choosing an approach | 3-6 sources, compare, recommend |
| very thorough | architecture, redesign, "this has to be solved somewhere" | survey the field, name the canon, ROI-ordered options |
Fan out with parallel subagents for breadth. Give each one a scope, a
Thoroughness: level, Do not edit files., and a return contract: exact paths
with line numbers and short quotes for code, or URL, technique, license, and
applicability for outside repos.
Documents of record first
Exhaust what the project already states before searching the web.
- Tickets and specs: the tracker issue, the PRD or spec, QA feedback, the Slack or Discord thread that started it — whatever this project treats as the record.
- The repo's own planning docs:
plans/,docs/, ADRs,AGENTS.md,CONTEXT.md, README. - Figma dev mode when the question is visual. The design is the source of truth
(→
ui-system). - The repo itself:
git log -S<symbol>andgit log -pfor why the code got this way, and the vendored source innode_modulesor site-packages instead of a remembered API surface.
When two documents disagree, say so instead of silently picking one. "Double check against X, Y, Z" means re-read each one and answer per document, not re-skim your own diff.
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.
- 2mo ago First seen · 91 lines · 67 tokens per session scan A c3e4194045ab
research is a skill published in the GitHub repository OutThisLife/brooklyn-skills (209 stars, last pushed 7d ago), licensed MIT. It adds 67 tokens to every session and 968 once invoked, about $0.0003 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-30.
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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…