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 rockyflux/yq-workflow --skill research-note-wrapgit clone --depth 1 https://github.com/rockyflux/yq-workflowWrote 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/rockyflux/yq-workflow/research-note-wrap)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/research-note-wrap"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/research-note-wrap/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/rockyflux/yq-workflow/research-note-wrap"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/research-note-wrap.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.00095 | $0.01476 |
| Opus 5 | $0.00048 | $0.00738 |
| Sonnet 5 | $0.00019 | $0.00295 |
| Haiku 4.5 | $0.00010 | $0.00148 |
Grade A, and why
research-note-wrap 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 8d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
research-note-wrap
Overview
Summarize the current session, or today's related sessions for a given topic, into an Obsidian Markdown note that is easy to review later. Prioritize core problems, comparative analysis, and clear conclusions over code detail or process narration.
Core Rules
- Write in Simplified Chinese by default.
- Prioritize logical conclusions over coding details.
- Do not produce a chronological 流水账.
- Use tables first when comparing multiple problems, hypotheses, conclusions, impacts, or next actions.
- After the tables, provide a short
关键结论section. - Only include code-level details when they are truly necessary to support the conclusion.
- If you mention a file, function, method, or code path, explain in Chinese:
- what it does
- why it matters
- how it supports the conclusion
- Default to writing the note file after confirmation; do not stop at chat-only output unless the user explicitly asks not to write a file.
Scope Decision
Default scope
If the user says things like:
- 总结调研
- 输出结论
- 总结分析
- 输出笔记
- 调研纪要
- 分析纪要
- 会话结论
Then summarize the current session only.
Cross-session scope
If the user says things like:
- 总结今天会话关于 xx 的分析
- 汇总今天关于 xx 的调研
- 总结今天相关会话中的 xx 问题
Then collect today's related sessions about the given topic and synthesize them into one note.
If the user explicitly provides another time range, follow that range. Otherwise, 近期 defaults to 当天.
Output Location Decision
Before writing the file:
- Check whether the current project's
AGENTS.mdexplicitly defines a default output directory for research / analysis summary notes. - If
AGENTS.mdalready defines it, follow that path directly. - If it does not define a path, ask the user for the output directory the first time.
- Once the user gives a path, use it for the current task. Suggest adding it to
AGENTS.mdif this is a recurring workflow.
Confirmation Workflow
Do not write the file immediately after the first draft. Use this confirmation sequence:
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.
- 8d ago First seen · 207 lines · 95 tokens per session scan A d4b7ac4db43a
research-note-wrap is a skill published in the GitHub repository rockyflux/yq-workflow (2 stars, last pushed 3mo ago), licensed MIT. It adds 95 tokens to every session and 1,476 once invoked, about $0.0005 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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…