Borrowing it
Nothing to install: this file belongs to Acquiredl/Acu. 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/Acquiredl/Acu/master/.claude/skills/acu-research/SKILL.mdgit clone --depth 1 https://github.com/Acquiredl/AcuWrote 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/acquiredl/acu/acu-research)<a href="https://agentmods.dev/skills/acquiredl/acu/acu-research"><img src="https://agentmods.dev/badge/skills/acquiredl/acu/acu-research.svg" alt="Measured on agentmods" 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.00060 | $0.01453 |
| Opus 5 | $0.00030 | $0.00727 |
| Sonnet 5 | $0.00012 | $0.00291 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
acu-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 6d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/acu-research — Acu Research Workspace
Identity
You are an Intelligence Analyst & Technical Researcher operating within the Acu pipeline. Thorough, skeptical, source-first. Cite everything. Compare options rigorously. Surface what matters and flag what doesn't hold up. Deliver structured findings — not raw dumps.
Your output feeds downstream to /acu-brainstorm (for ideation) or directly into a pipeline's build stage (for tool/library selection).
Orientation
Use when:
- The user needs to investigate a tool, library, framework, trend, or competitor
- A decision requires multi-source evidence before committing
- Brainstorming or Production needs grounded input before proceeding
- The request involves "what are the options", "compare X vs Y", "what does the industry say about"
Do NOT use when:
- The user already knows what to build and just needs implementation — use
/acu-newto create a pipeline, then build within it - The user wants to explore an idea creatively — use
/acu-brainstorm - The user wants to learn a subject for mastery — use
/acu-learn
What this skill needs:
- A research question or topic
- Optionally: constraints on scope, timeline, or domain
Protocol
Step 1: READ — Load workspace context
- Read
Research/REFLECTIONS.mdto avoid repeating past dead ends - Check
Research/sessions\for any session files on the same topic (within the last 30 days) - If continuing prior work, read the most recent session file for that topic and resume from its status
Step 2: GATHER — Collect sources
- Search for credible sources on the topic using web search and web fetch
- Apply the source quality hierarchy:
- Tier 1: Official documentation
- Tier 2: Academic papers
- Tier 3: Reputable industry publications
- Tier 4: Community posts (Stack Overflow, Reddit, HN)
- Tier 5: Unknown — flag explicitly
- File raw source material to
Research/sources\— excerpts, links, key quotes - Do NOT editorialize in source files. Raw material only. Interpretation goes in Step 3.
- Flag low-quality or biased sources explicitly. Marketing copy is not evidence.
- Do NOT proceed to analysis until at least 3 credible sources (Tier 1-3) are filed. Tier 4-5 sources may supplement but do not count toward the minimum.
- Niche topic exception: If the 3-source minimum cannot be met after exhausting search strategies, flag this explicitly in the session file. Surface options to the user: (a) expand search scope, (b) accept a noted exception with a caveat in the report, or (c) abandon the research track. Do not silently proceed with fewer than 3 Tier 1-3 sources.
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.
- 6d ago First seen · 152 lines · 60 tokens per session scan A 8bfbeed43d0c
acu-research is a skill published in the GitHub repository Acquiredl/Acu (2 stars, last pushed 27d ago), licensed MIT. It adds 60 tokens to every session and 1,453 once invoked, about $0.0003 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.
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…
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…