Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hlalljie/agent-workflow-presets/main/.cursor/skills/research/SKILL.mdgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/research)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/research"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/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/hlalljie/agent-workflow-presets/research"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/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.00051 | $0.01058 |
| Opus 5.5 | $0.00020 | $0.00423 |
| Sonnet 5.5 | $0.00010 | $0.00212 |
| Haiku 4.5 | $0.00005 | $0.00106 |
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 19d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research
When to use
Invoked explicitly when a decision needs information gathering. Always spawn a subagent to execute this skill. Not every question needs a full research doc — if a quick web search answers it, just answer in chat. Use this skill when the topic is complex, has multiple options to weigh, or will be referenced later.
Doc or chat
Default: report the findings in chat and write no file. Write a doc only when one of these is true:
- The findings need a lot of reading, so a chat reply would be too long.
- A future session needs them recorded.
If unsure, answer in chat. Everything below about the doc applies only when one is written.
A research doc is standalone. It does not contain status markers, links to open questions, or links to plans. Other docs in the same plan link to it; it links to nothing upstream. Nothing outside .cursor/plans/ links to it, because the plan folder moves when the plan finishes.
File location: .cursor/plans/<plan-name>/research/<topic>.md.
Process
- Clarify what the user is asking. A research doc can cover multiple related questions if they naturally group together — it is organized around a topic, not rigidly one-question-per-file.
- Gather local context before searching, unless the question is general or the invoker already has it. Read what the project already says about the topic (docs, rules, skills,
docs/decisions.md, plans, related earlier work) so the research fits what exists and does not repeat it. This skill runs as a subagent: the invoker puts what it knows in the subagent prompt, and the subagent reads the rest. - Search broadly (multiple queries, different angles).
- Fetch and read promising sources before citing them. If a source looks relevant but cannot be read (paywall, video, etc.), move on unless nothing else covers that ground — then link it with a note.
- Discard junk. A source earns its place by directly informing the user's question. Do not pad with tangentially related links.
- If a doc is warranted (see Doc or chat), write it.
- Tell the user what you found.
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.
- 19d ago Changed · +2 lines 157f283c9eb8
- 22d ago Changed · +9 lines · +15 tokens per session 43e3e9792803
- 1mo ago First seen · 55 lines · 36 tokens per session scan A 622b3a30de44
research is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 20d ago), licensed MIT. It adds 51 tokens to every session and 1,058 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
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
review-a-skill
Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.
audit-library-health
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
build-workspace-docs
Use when regenerating README.md and WORKAREAS.md in a managed library workspace. Always dry-run first to preview changes.
update-installed-skills
Use when syncing or updating previously installed skills to their latest version. Always dry-run updates before applying, and check for breaking changes.