Borrowing it
Nothing to install: this file belongs to Hwiyeon/claude-sisyphus-grad. 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/Hwiyeon/claude-sisyphus-grad/main/.claude/skills/research-log/SKILL.mdgit clone --depth 1 https://github.com/Hwiyeon/claude-sisyphus-gradWrote 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/hwiyeon/claude-sisyphus-grad/research-log)<a href="https://agentmods.dev/skills/hwiyeon/claude-sisyphus-grad/research-log"><img src="https://agentmods.dev/badge/skills/hwiyeon/claude-sisyphus-grad/research-log/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/hwiyeon/claude-sisyphus-grad/research-log"><img src="https://agentmods.dev/badge/skills/hwiyeon/claude-sisyphus-grad/research-log.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.00018 | $0.00749 |
| Opus 5 | $0.00009 | $0.00375 |
| Sonnet 5 | $0.00004 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
research-log 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 13d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Log Templates & Directory Structure
Directory Structure
research/
├── CLAUDE.md ← operating rules (auto-loaded each session)
├── README.md ← research status summary (shown on GitHub)
├── logs/
│ ├── YYYY-MM-DD/ ← daily log folder (current week)
│ │ ├── log.md ← Deep-Dive research log
│ │ └── *.png/jpg ← experiment result visualizations
│ └── archive/
│ └── MMDD~MMDD/ ← weekly folder (contains daily folders)
├── summaries/ ← weekly (week-MMDD~MMDD.md) / monthly summaries
├── topics/ ← topic-specific cumulative notes
│ └── <topic>/
│ ├── architecture_<topic>.md ← current best specification
│ ├── experiment_log.md ← architecture changelog
│ ├── log.md ← module-specific cumulative log
│ └── discussion/ ← in-depth topic discussion docs
└── related_work/ ← related papers/techniques
log.md Writing Structure
=============================================================================
[Deep-Dive Research Log]
Context Header: YYYY-MM-DD / main topics
=============================================================================
■ Current Objectives
- Today's discussion goals and specific bottlenecks to resolve
■ The 'Missing' Details (Trials & Failures)
- Ideas discussed but not adopted, with specific rejection reasons
- Excluded variables and technical rationale
- Unresolved questions
■ Confirmed Decisions
- Finalized algorithms, model structures, formulas, parameters, hard constraints
■ Architecture Update (if applicable)
- Changed inputs/outputs, new layers/modules, loss, config, etc.
- ASCII Art architecture diagram
■ Technical Artifacts
- Key formulas (KaTeX: $$...$$ block, $...$ inline)
- Key code snippets
■ Experiment Results (if applicable)
- Training curves, metric trends, visualization results
- Images: saved in same folder, referenced by relative path 
■ Future Directions
- Priority To-Do items to tackle first in tomorrow's session
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.
- 13d ago First seen · 88 lines · 18 tokens per session scan A 6214e67f0585
research-log is a skill published in the GitHub repository Hwiyeon/claude-sisyphus-grad (59 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 749 once invoked, about $0.0001 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-30.
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…