Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add octavehq/lfgtm/plugin install octaveWrote 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/octavehq/lfgtm/research)<a href="https://agentmods.dev/skills/octavehq/lfgtm/research"><img src="https://agentmods.dev/badge/skills/octavehq/lfgtm/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.
<a href="https://agentmods.dev/skills/octavehq/lfgtm/research"><img src="https://agentmods.dev/badge/skills/octavehq/lfgtm/research.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.00126 | $0.07460 |
| Opus 5 | $0.00063 | $0.03730 |
| Sonnet 5 | $0.00025 | $0.01492 |
| Haiku 4.5 | $0.00013 | $0.00746 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 561 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/octave:research - Context-Aware Research & Prep
Research prospects and prepare for calls, meetings, demos, outreach, and deal reviews. Adapts output based on the occasion and format — whether you're prepping for a discovery call, following up on a deal, or researching a new prospect. Supports two output formats:
- Text (default) — plain-text research output, optimized for quick consumption in chat
- HTML — a styled, self-contained HTML account brief with sticky navigation, collapsible sections, and print-friendly layout, designed to sit on your second monitor during a call or to review before a meeting
Key differentiators:
- vs
/octave:one-pager— one-pager is customer-facing; research (HTML) is internal prep - vs
/octave:deck— deck is a slide presentation; research (HTML) is a scrollable reference document
On-brand styling (HTML format only): workspace company's brand, target logo in content
Resolve the brand before generating (do not skip this step). The document brand is the workspace company's brand: the Octave customer whose workspace is running the skill. The target company's logo (the account being researched) appears in content only (e.g., the header's "prepared for" line, the company snapshot card) and never controls the design system. See brand kit usage for the full model, cache lookup, and extraction tiers.
- Call
get_workspace_companyto resolve the workspace company (name, domain, positioning): this is whose brand the brief wears. - Slugify the workspace company name and check for a cached brand kit at
~/.octave/brands/<slug>/manifest.json. If a complete kit exists, use it automatically:- inline the kit's
tokens.css(:root+ the embedded@font-face) andget-brand-components/assets/kit_base.cssinto the output<style>; - follow
brand-kit.md--> Signature moves, and reuse the kit's real logo,images/, andicons.json; - for doc-shaped output you can compose directly with
get-brand-components/scripts/render_kit.py(hero / split / logos / pricing / cta / footer blocks).
- inline the kit's
- If no kit exists --> offer to build one first: "No brand kit for yet, want me to capture it (~1 min) so this is on-brand?" --> run
/octave:get-brand-components <workspace-domain>, then proceed. - Fetch the target company's logo with
get_external_brand_logo/get_external_brand_assetsand place it in content (company snapshot, header "prepared for" line), not in the chrome. - If the user declines a kit --> generate with the default style/preset.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 561 lines · 126 tokens per session scan A 648b817df397
research is a skill published in the GitHub repository octavehq/lfgtm (11 stars, last pushed 20d ago), licensed MIT. It adds 126 tokens to every session and 7,460 once invoked, about $0.0006 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…