Borrowing it
Nothing to install: this file belongs to mickeytony0215-png/obsidian-llm-wiki. 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/mickeytony0215-png/obsidian-llm-wiki/main/.claude/commands/paper-report.mdgit clone --depth 1 https://github.com/mickeytony0215-png/obsidian-llm-wikiWrote 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/mickeytony0215-png/obsidian-llm-wiki/paper-report)<a href="https://agentmods.dev/commands/mickeytony0215-png/obsidian-llm-wiki/paper-report"><img src="https://agentmods.dev/badge/commands/mickeytony0215-png/obsidian-llm-wiki/paper-report/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/mickeytony0215-png/obsidian-llm-wiki/paper-report"><img src="https://agentmods.dev/badge/commands/mickeytony0215-png/obsidian-llm-wiki/paper-report.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.00016 | $0.00569 |
| Opus 5 | $0.00008 | $0.00284 |
| Sonnet 5 | $0.00003 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
paper-report 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 12d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review-gate check (soft)
Before running, check review_status:
unreviewed: warn — "This note has not been audited. A seminar report built on top of it may inherit errors. Running/review-notefirst is strongly recommended. (The seminar-report flow overlaps heavily with the audit flow anyway, so this is a good time to do both.)"- If the user continues, prepend:
> [UNREVIEWED] This report is based on an unreviewed note. Treat the PDF as the final authority.
- If the user continues, prepend:
disputed: continue, but the critical-analysis section must surface the specific concerns (e.g. perfect arithmetic progressions, in-text/table contradictions)reviewed_with_notes: quote the existingreview_notesconcerns in the critical-analysis sectionreviewed: run normally
Tip: The seminar-report flow (especially step 2 "claim-by-claim PDF check") overlaps heavily with /review-note. Treat seminar preparation as a deep-audit opportunity — once done, the user can upgrade review_status to reviewed_with_notes / disputed (if issues were found) and sync findings to the note's ## Review log and to wiki/review-history.md.
Main flow
Read the PDF I specify plus the paper note I have open, then write a seminar-report draft.
Step 1: Load sources
- Read the full PDF content
- Read the comments and reactions in the note
- Use the PDF as the primary information source; use the note as commentary
Step 2: Write the report
Structure:
- Background and motivation
- Related work (brief summary of 2–3 related studies)
- System model and problem definition
- Proposed method (core architecture and algorithm)
- Experimental results and analysis
- Critical analysis (strengths, weaknesses, logical-consistency check)
- Relation to my research
- Conclusion
Step 3: Build links
- Use
[[wikilinks]]in the new note to connect related notes - Add reverse links in those related notes
Requirements
- Use the output language specified in SKILL.md (keep technical terms in their original form).
- The critical-analysis section must have depth — concretely state whether motivation and methodology align.
- Preserve and integrate the user's personal critique from the source note.
- Where possible, suggest how the method could extend to the user's own domain.
- File name for the new note:
seminar-report-{paper-slug}-{YYYY-MM-DD}.mdat vault root.
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.
- 12d ago First seen · 53 lines · 16 tokens per session scan A 7dad915a2b2f
paper-report is a command published in the GitHub repository mickeytony0215-png/obsidian-llm-wiki (2 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 569 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-31.
Other commands, from other repositories
daily-okr
Run a daily knowledge compound loop (7 KR). Invoke with /daily-okr or "start my daily review".
session-learn
Extract knowledge from the current session. Invoke with /session-learn or "extract this session".
status
Show memex statistics and status including projects, memos, and pending items.
open
Open the memex vault in Finder or Obsidian.
okf
A command that exports a private knowledge wiki into an OKF-compatible bundle. OKF is a format for packaging knowledge, with a separate guarded mode for preparing material to share externally.
ingest
A command for adding information to a file-based knowledge wiki from web pages, files, or text notes. It classifies the material, updates or creates wiki pages, and adds links between related pages.