Borrowing it
Nothing to install: this file belongs to RosMarinas/Research-Pi. 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/RosMarinas/Research-Pi/main/.pi/skills/research-briefing/SKILL.mdgit clone --depth 1 https://github.com/RosMarinas/Research-PiWrote 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/rosmarinas/research-pi/research-briefing)<a href="https://agentmods.dev/skills/rosmarinas/research-pi/research-briefing"><img src="https://agentmods.dev/badge/skills/rosmarinas/research-pi/research-briefing/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/skills/rosmarinas/research-pi/research-briefing"><img src="https://agentmods.dev/badge/skills/rosmarinas/research-pi/research-briefing.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.00064 | $0.00452 |
| Opus 5 | $0.00032 | $0.00226 |
| Sonnet 5 | $0.00013 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
research-briefing 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 11d 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
Research Briefing
Produce the shortest explanation that restores the shared research state needed for the user's next judgment.
Before writing, recover the relevant ProjectView live delta, experiment record, delegated result, run identity, or artifact. Treat compacted state and assistant prose as navigation; verify a consequential factual claim against the strongest available record.
Select, rather than mechanically enumerate, the parts the user currently needs:
- orientation: where this result sits in the current stage and what question was open;
- work: what the Leader, Codex, or another actor actually changed, compared, or ran;
- evidence: the decision-carrying observation, comparison, and minimum validity check;
- interpretation: which hypothesis or route is supported, weakened, untested, or still ambiguous, including the main boundary on that claim;
- consequence: what changed in the research plan and what next question or decision now has the highest value.
Keep work, observation, validity, interpretation, and plan logically distinct even when presenting them as natural prose rather than headings. A completed task or commit is not itself evidence for a research claim.
Write for a technically capable collaborator who may not have read the intermediate transcript:
- lead with the result and why it matters;
- use explicit actors, actions, comparisons, and causal connectors;
- explain a local term or acronym once when it becomes necessary;
- attach important numbers to their metric, baseline, threshold, or uncertainty;
- use one concrete project example or compact analogy when it reduces conceptual load, then state the technical meaning;
- translate internal JSON, ledger terms, and subagent shorthand instead of forwarding them;
- omit recaps the user has already demonstrated they understand.
If ProjectView is stale, describe its structured state as the pre-result baseline and integrate the pending evidence delta before stating the current position. Do not silently promote a Codex recommendation or an unvalidated run into the project's conclusion.
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.
- 11d ago First seen · 33 lines · 64 tokens per session scan A 00f28e6ec88a
research-briefing is a skill published in the GitHub repository RosMarinas/Research-Pi (6 stars, last pushed 5d ago), licensed MIT. It adds 64 tokens to every session and 452 once invoked, about $0.0003 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
harness-creator
Build, audit, and improve harnesses that make AI coding agents reliable: AGENTS.md/CLAUDE.md instruction files, feature/state tracking, verification gates, scope boundaries, session handoff, memory persistence, context budgets, tool-permission safety, and multi-agent coordination. Use this whenever a coding agent is…
temporal
Resolve ANY named time window — today, yesterday, thisWeek, lastWeek, last7Days, last30Days, last90Days, thisMonth, lastMonth, thisQuarter, lastQuarter, thisYear, lastYear, last12Months — or an arbitrary range (lastNdays / lastNweeks / lastNmonths) to a concrete ISO date range relative to your run time. Read-only: no…
last30Days
Resolve "last30Days" to a concrete ISO date range relative to your run time — a rolling 30-day window ending today. Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a "last 30 days" / trailing-month task…
thisQuarter
Resolve "thisQuarter" to a concrete ISO date range relative to your run time — this quarter so far (quarter start → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a quarter-to-date task (QTD…
thisWeek
Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…
harness
A meta-skill for designing and maintaining a project harness: a coordinated set of specialist agents, skills, and project instructions. It defines their roles, connects them to the project, and updates the setup as the work changes.