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/skills/research-workflow/SKILL.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/skills/arnaudgelas/k-ops/research-workflow)<a href="https://agentmods.dev/skills/arnaudgelas/k-ops/research-workflow"><img src="https://agentmods.dev/badge/skills/arnaudgelas/k-ops/research-workflow.svg" alt="Measured on agentmods" 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.00029 | $0.00788 |
| Opus 5 | $0.00015 | $0.00394 |
| Sonnet 5 | $0.00006 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
research-workflow 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 6d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Workflow
Goal
Run higher-stakes topics as resumable, tiered research threads outside the curated vault until they are ready to promote.
Use When
- The user wants a structured research run rather than an immediate vault answer.
- A topic needs source collection, contrarian review, and a final report.
- An external model report should be imported as a lead, not treated as authority.
Core Flow
- Start a run:
uv run kops research-start --topic "<text>" --tier <fast|standard|deep>. - Check status:
uv run kops research-status [topic|all]. - Collect sources:
uv run kops research-collect --agent <codex|claude|gemini> --topic "<topic>"(runs collect prompt). - Adversarial review:
uv run kops research-review --agent <codex|claude|gemini> --topic "<topic>"(runs review prompt). - Draft report:
uv run kops research-report --agent <codex|claude|gemini> --topic "<topic>"(runs report prompt). - Import external reports:
uv run kops research-import --topic "<topic>" --path <file> --provider <provider> --origin <origin>. - Archive completed run:
uv run kops research-archive --topic "<topic>"(after phase showsdone).
Phase Guidance
The research-collect, research-review, and research-report CLI subcommands render their own runtime prompts (from kops/templates/), so no separate skill is needed. When running or reviewing a phase by hand, hold to these contracts:
- Collect (
research-collect): populate the findings file with high-signal, sourced claims. Create/update source notes innotes/Sources/under the strict metadata schemas; prefer primary sources; mark imported model reportsauthority: lead_only+verification_state: needs_primary_sources. Distinguish evidence from inference; keep uncertainty explicit; append a progress log. - Review (
research-review): adversarial contrarian pass — try to break the thesis, not confirm it. Populate## Strongest Objections,## Missing Evidence,## Claims To Softenwith genuine gaps (never fabricated counter-evidence); name missing primary sources to consult before drafting. - Report (
research-report): synthesize brief + sources + findings + contrarian review into a bounded report. Build from collected evidence only, address the strongest objections, keep conclusions bounded by evidence, cite source summaries with wikilinks, and distinguish established from provisional findings.
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.
- 6d ago First seen · 45 lines · 29 tokens per session scan A 563e36cafa2c
research-workflow is a skill published in the GitHub repository arnaudgelas/K-Ops (1 stars, last pushed 18d ago), licensed MIT. It adds 29 tokens to every session and 788 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 skills, from other repositories
kb-lint
Health check for the PARA Knowledge Base. Detects orphan documents, broken links, index drift, tag issues, and stale content. Run periodically or as part of weekly review.
kb-index
Update Knowledge Base indexes. Smart mode detects changes and updates only what's needed. Full rebuild available with --full flag. Use after adding/moving documents or when indexes feel stale.
wiki-ingest
Ingest exactly one research paper or source document into an open-llm-wiki vault. Use when the user explicitly asks to add, ingest, process, or publish a paper into the wiki. The workflow parses the source, drafts a source page, runs independent QA, publishes only after the quality gate passes, extracts and normalizes…
query-writeback
Answer cross-source questions about an open-llm-wiki vault and optionally write reusable synthesis back into concept pages. Use when the user asks a wiki question that requires comparing, connecting, or tracing multiple source/concept pages. By default answer first and propose writeback; modify files only when the…
wiki-lint
Run a health check for an open-llm-wiki vault. Use when the user asks to lint, audit, validate, or periodically check wiki quality. The default mode is report-only: inspect schema compliance, QA coverage, links, stale claims, contradictions, and log health. Modify files only when the user explicitly requests fix mode…
wiki-lint
Audit and maintain the health of the Obsidian wiki. Use this skill when the user wants to check their wiki for issues, find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks, or perform general maintenance on their knowledge base. Also triggers on "clean up the wiki", "what needs…