objective-research

objective-research is a skill for Claude Code, Codex from mlopscommunity/Coding-Agents-Conference-skills. It costs 43 tokens per session (1,931 once invoked), scanned A, original, Apache-2.0.

A research method that separates understanding what you want to build from investigating how the existing code works.

In plain words
What is it for?
Use it to trace calls and data, understand schemas, and map an existing feature before changing unfamiliar code.
Why use it?
Keeping the coding plan away from the investigation reduces the risk of treating guesses as facts or overlooking alternatives in the codebase.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to trace calls and data, understand schemas, and map an existing feature before changing unfamiliar code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mlopscommunity/coding-agents-conference-skills/objective-research
Install

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.

Any agent
npx skills add mlopscommunity/Coding-Agents-Conference-skills --skill objective-research
Clone the repo
git clone --depth 1 https://github.com/mlopscommunity/Coding-Agents-Conference-skills

Made for: Claude Code, Codex.

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 objective-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/mlopscommunity/coding-agents-conference-skills/objective-research/github.svg)](https://agentmods.dev/skills/mlopscommunity/coding-agents-conference-skills/objective-research)
Your own site
<a href="https://agentmods.dev/skills/mlopscommunity/coding-agents-conference-skills/objective-research"><img src="https://agentmods.dev/badge/skills/mlopscommunity/coding-agents-conference-skills/objective-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 objective-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/mlopscommunity/coding-agents-conference-skills/objective-research"><img src="https://agentmods.dev/badge/skills/mlopscommunity/coding-agents-conference-skills/objective-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,931 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.00043 $0.01931
Opus 5.5 $0.00017 $0.00772
Sonnet 5.5 $0.00009 $0.00386
Haiku 4.5 $0.00004 $0.00193

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

Security

Grade A, and why

objective-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 2mo 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.

skills/objective-research/SKILL.md · 157 lines

How it starts

The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Objective Research via Context Separation

Overview

A two-context technique for producing unbiased codebase research. The first context (intent context) knows what you are building and decomposes the ticket into targeted research questions. The second context (research context) receives only those questions — never the ticket — and returns compressed factual findings about how the code works today.

Core principle: If the research agent knows what you are building, it injects opinions into facts. Confirmation bias causes it to emphasize code paths that support the anticipated solution and downplay alternatives. Separate intent from investigation.

When to Use

  • Before starting implementation on a ticket that touches unfamiliar code
  • When you need to understand how an existing feature works end-to-end
  • When tracing data flow, call paths, or schema shapes across multiple files
  • Any time research quality matters more than speed

When NOT to Use

  • Trivial changes where you already understand the code
  • Pure greenfield work with no existing code to investigate
  • Quick lookups (e.g., "what version of React is installed")

Common Mistakes

Mistake Why it's wrong
Giving the research agent the full ticket It will shape findings to match the anticipated solution. You get confirmation, not truth.
Asking broad, open-ended research questions "How does auth work?" produces a rambling survey. Targeted questions like "What function validates JWT expiry and what does it return on failure?" produce usable facts.
Mixing factual questions with design questions "What's the best way to add caching here?" is a design opinion, not research. Research should describe what exists, not what should exist.
Skipping the question-generation step Jumping straight into research without decomposing the ticket means you investigate reactively — following whatever catches your eye — instead of systematically covering what you need to know.
Reusing the same context for research and implementation The implementation context has intent. If it also does the research, the same bias problem returns. Use a fresh context for investigation.

Read the full file on GitHub · 157 lines

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. 2mo ago First seen · 157 lines · 43 tokens per session scan A f9267b0eaee8

Subscribe to this mod's changes

objective-research is a skill published in the GitHub repository mlopscommunity/Coding-Agents-Conference-skills (39 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,931 once invoked, about $0.0002 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-30.

Related

objective-research compared with skills from other repositories

objective-research next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
objective-researchmlopscommunity/Coding-Agents-Conference-skillsSkill397mo agoApache-2.0A43Claude Code, Codex
imagegenopenai/codexSkill135ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill100ktodayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k5d agoMITA200Claude Code, Codex
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
systematic-debuggingobra/superpowersSkill316k8d agoMITA21Claude Code