Borrowing it
Nothing to install: this file belongs to arnaudgelas/K-Ops. 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/arnaudgelas/K-Ops/main/.claude/commands/research_report.mdgit clone --depth 1 https://github.com/arnaudgelas/K-OpsWrote 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/arnaudgelas/k-ops/research_report)<a href="https://agentmods.dev/commands/arnaudgelas/k-ops/research_report"><img src="https://agentmods.dev/badge/commands/arnaudgelas/k-ops/research_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/arnaudgelas/k-ops/research_report"><img src="https://agentmods.dev/badge/commands/arnaudgelas/k-ops/research_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.00002 | $0.00536 |
| Opus 5.5 | $0.00001 | $0.00214 |
| Sonnet 5.5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
research_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 1mo 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
You are the Research Report agent for this repository.
Goal:
- Draft the final research report synthesizing the brief, findings, and contrarian review into a bounded, evidence-grounded deliverable.
Inputs:
- Research brief: research/briefs/-.md
- Findings file: research/findings/-.md
- Review file: research/notes/-contrarian-review.md
- Report file: research/reports/-.md
Instructions:
- Synthesize inputs: Read the brief, findings, source notes, and contrarian review thoroughly.
- Draft the report:
- Write/update
research/reports/<topic-slug>-<date>.md. Preserve its frontmatter (type:research-report,topic_slug, etc.). - Under
## Executive Summary, provide a high-level overview of the findings, conclusions, and engineering recommendations. - Under
## Methodology, briefly detail the source collection and review process. - Under
## Evidence and Analysis, write the core sections. Every key fact or claim must be directly cited with Obsidian wikilinks to the source summaries (e.g.[[Sources/src-<id>|src-<id>]]). Group findings logically. - Under
## Engineering Recommendations, list concrete actionable steps derived from the evidence. - Under
## Contradictory or Missing Evidence, explicitly address each objection and gap raised in the contrarian review and document remaining uncertainties or contradictions between sources. - Under
## Source Map, list all concept pages and source summaries (with Obsidian wikilinks) that informed this report.
- Write/update
- Evidence bounds:
- Keep conclusions strictly bounded by the collected evidence. Avoid making general or sweeping assertions that aren't backed by the cited sources.
- If a claim relies on an imported model report, ensure it has been verified against a primary source before including it in the report.
- Progress Log: Append a short progress update when done.
Done checklist:
- Completed report saved in
research/reports/<topic-slug>-<date>.mdwith all required sections (Executive Summary, Methodology, Evidence and Analysis, Engineering Recommendations, Contradictory or Missing Evidence, Source Map) populated. - All claims are backed by source citations.
- Objections from the contrarian review are addressed or documented as open questions.
- No placeholders remain in the report.
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.
- 1mo ago First seen · 37 lines · 2 tokens per session scan A 6542a23a25ff
research_report is a command published in the GitHub repository arnaudgelas/K-Ops (1 stars, last pushed 2mo ago), licensed MIT. It adds 2 tokens to every session and 536 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
wiki-req
Capture and decompose a concept into atomic, traceable wiki requirements. Clarifies ambiguous requirements, splits them into atomic pieces, and persists them as wiki/requirements/ pages with status tracking.
wiki-retro
Save an atomic insight from the current task into the wiki. Creates a single markdown file that layered recall surfaces in future sessions.
wiki-discover
Auto-discover new sources from the web. Searches based on config topics and known knowledge gaps.
wiki-run
Run the full wiki cycle: discover → ingest → lint. Optionally schedule for auto-updates.
wiki-digest
Generate a daily or weekly digest of wiki changes — new sources, pages, insights, and gaps.
wiki-lint
Health check the wiki. Detects contradictions, orphans, missing pages, stale claims, and knowledge gaps.