mscodebase-intelligence: Command for OpenCode

.opencode/command/research.md

research is a command for OpenCode from ManSio/mscodebase-intelligence. It costs 15 tokens per session (418 once invoked), scanned A, original, MIT.

A research command for answering a specific question from primary sources, such as a paper, specification, release note, or source code. It records the question, what would disprove it, sources, negative searches, and effects on the code.

In plain words
What is it for?
Use it before building on a protocol, rule, tool, or technical claim, especially when the result must be tied to a concrete file or code change.
Why use it?
It prevents treating a summary or memory as verified evidence and preserves useful searches that found nothing. It also separates facts checked during the session from facts merely recalled.

Command for OpenCode

Written for OpenCode: installed under .opencode/.

This is ManSio/mscodebase-intelligence's own configuration. It tells OpenCode how to work on mscodebase-intelligence itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mscodebase-intelligence configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ManSio/mscodebase-intelligence. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ManSio/mscodebase-intelligence/main/.opencode/command/research.md
Clone the repo
git clone --depth 1 https://github.com/ManSio/mscodebase-intelligence

Made for: OpenCode.

Wrote 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.

agentmods badge for research

README.md
[![agentmods](https://agentmods.dev/badge/commands/mansio/mscodebase-intelligence/research/github.svg)](https://agentmods.dev/commands/mansio/mscodebase-intelligence/research)
Your own site
<a href="https://agentmods.dev/commands/mansio/mscodebase-intelligence/research"><img src="https://agentmods.dev/badge/commands/mansio/mscodebase-intelligence/research/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.

agentmods 80×15 button for research

Your own site · 80×15
<a href="https://agentmods.dev/commands/mansio/mscodebase-intelligence/research"><img src="https://agentmods.dev/badge/commands/mansio/mscodebase-intelligence/research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 418 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00418
Opus 5.5 $0.00006 $0.00167
Sonnet 5.5 $0.00003 $0.00084
Haiku 4.5 $0.00002 $0.00042

Measured 26d ago against content hash e61a578fea04, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

research 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 26d 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.

.opencode/command/research.md · 50 lines

What it actually says

You are running the RESEARCH phase of the protocol. Your only job is to produce facts the owner can decide on. You are not deciding.

Order of work

  1. State the question and its falsifier. "Does X work?" is not a question. "Under what condition is X wrong?" is. Write both down before searching.
  2. Search for the primary source, not the summary. A blog post about a paper is not a source. Prefer the paper, the spec, the release notes, the code.
  3. Record the negative result. A search that returned nothing useful is data. Write which query failed and what it should have returned. A quietly wrong search result is worse than an empty one — it looks like an answer.
  4. Freeze the input before you look at the result if this is an experiment rather than a reading task. See experiments/*/frozen/.
  5. Separate Verified from Recalled. Anything you did not open in this session is Recalled and must be marked so.

Output

## [🔍 ИССЛЕДОВАНИЕ] <subject>

**Question:** ...
**Falsified if:** ...

**Sources**
| source | what it establishes | verified how |

**Negative results**
- query → what it failed to find

**What this changes in our code**
- concrete file:line, or "nothing"

**Still unknown**
- the question this does NOT answer

Rules

  • Two contradictory sources: report both, do not average them.
  • A claim with a number gets a referent, or it does not go in the report.
  • Do not recommend an action. Present options and their costs; the owner decides.
  • If the research contradicts something we published, that is the most important line in the report. Put it first.
Changes

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.

  1. 26d ago First seen · 50 lines · 15 tokens per session scan A e61a578fea04

Subscribe to this mod's changes

research is a command published in the GitHub repository ManSio/mscodebase-intelligence (3 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 418 once invoked, about $0.0001 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-10-04.