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.
git clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/commands/khaledsaeed18/dotclaude/research-log)<a href="https://agentmods.dev/commands/khaledsaeed18/dotclaude/research-log"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/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/commands/khaledsaeed18/dotclaude/research-log"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/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.00081 | $0.00642 |
| Opus 5.5 | $0.00032 | $0.00257 |
| Sonnet 5.5 | $0.00016 | $0.00128 |
| Haiku 4.5 | $0.00008 | $0.00064 |
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 25d 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.
What it actually says
Context
Today: !date +%Y-%m-%d
Notes added or changed in the last 7 days:
!find research/notes -name '*.md' -mtime -7 2>/dev/null | sort || echo "(no research/notes directory)"
Commits in the last 7 days:
!git log --since='7 days ago' --format=' %ad %s' --date=short 2>/dev/null || echo "(not a git repository)"
Working tree:
!git status --short 2>/dev/null | head -20
Last log entry:
!awk '/^## /{n++} n==1' RESEARCH_LOG.md 2>/dev/null | head -40 || echo "(no RESEARCH_LOG.md yet)"
Task
Append one entry to RESEARCH_LOG.md (create it with a # Research log heading if absent). Entries are newest-first, so insert after the title, before the previous entry.
Arguments, if any: $ARGUMENTS. Treat them as the student's own summary and fold them in verbatim under the right headings; do not rephrase their words.
Entry format
## 2026-09-21
### Read
- smith2023feedback: one line on what it contributed to the thesis (from the note's "Relation to this thesis").
### Did
- What was built, run, analysed, or written, with paths or commit hashes.
### Decided
- Decisions made, each with the reason and what it rules out. Link to research/QUESTION.md or a note where relevant.
### Open
- Questions for the supervisor, blockers, things that need data or approval.
### Next
- The two or three concrete next actions.
Rules
- Every bullet must be traceable: a note file, a commit, a path, or something the student said in this session. Do not infer activity from silence.
- Omit a heading with nothing under it rather than writing "nothing".
- Keep "Decided" honest: a decision reversed later is recorded as a new decision, not edited out.
- If the "Open" list has items older than two entries, say so in the reply; those need a supervisor.
- After writing, print the new entry and the count of entries in the log.
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.
- 25d ago First seen · 63 lines · 81 tokens per session scan A 324d937687f1
research-log is a command published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 642 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-09-22.
Other commands, from other repositories
support-model
Write a support model as Markdown in the user's repository. Produce designed HTML or PDF only when asked.
design-doc
Write a design doc / RFC as Markdown in the user's repository. Use when invoked as /document-design-system:design-doc. Produce designed HTML or PDF only when asked.
evaluate
Execute Evaluate stage to validate generated framework artifacts.
tutorial
Write a Diátaxis tutorial as Markdown in the user's repository. Use when invoked as /document-design-system:tutorial. Produce designed HTML or PDF only when asked.
ars-plan
ARS academic-paper plan mode — Socratic chapter-by-chapter planning.
checklist
Generate a custom checklist for the current feature based on user requirements.