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.
npx skills add octavehq/lfgtm --skill abmgit clone --depth 1 https://github.com/octavehq/lfgtmWrote 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/abm)<a href="https://agentmods.dev/skills/octavehq/lfgtm/abm"><img src="https://agentmods.dev/badge/skills/octavehq/lfgtm/abm/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/abm"><img src="https://agentmods.dev/badge/skills/octavehq/lfgtm/abm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 92 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00050 | $0.03673 |
| Opus 5 | $0.00025 | $0.01836 |
| Sonnet 5 | $0.00010 | $0.00735 |
| Haiku 4.5 | $0.00005 | $0.00367 |
Grade A, and why
abm 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 10d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/octave:abm - Account Planner
Create account plans for target accounts by combining deep research, stakeholder mapping, persona matching, and an engagement sequence — all grounded in your library's Motion ICP cells and proof points. Output is a self-contained HTML account plan.
What this skill is. The unit of /octave:abm is the account. It produces a tight, account-level plan a rep acts on, structured as six jobs: (1) is this account worth it and why now, (2) what's likely driving them / what to explore, (3) who to engage (buying committee), (4) how to position per persona, (5) the engagement plan, (6) what could go wrong. It DOES advise — per-persona positioning and an entry-point engagement plan are the point — but at the account level. The distinction from /octave:meeting-prep is scope: meeting-prep coaches one scheduled meeting (talk tracks, discovery, room game-plan); abm plans the whole account pursuit across the committee. Single-asset copy still lives in /octave:generate.
Groundedness is non-negotiable. Every named person, title, employer, and LinkedIn URL in the buying committee must come from a real find_person/enrich_person result. Never synthesize a person or a LinkedIn slug. Honest gaps beat plausible inventions. A prior run shipped a fabricated committee — do not repeat it.
Principles
Follow these standards during generation. Read each before producing output.
Content and language:
- Editorial rules — no AI-isms, banned vocabulary, honest analyst tone
- Information principles — lead with conclusions, evidence-backed claims, narrative arc
Presentation:
- Presentation principles — universal visual rules, spacing, restraint
- HTML document format — scrollable-document visual rules
Octave data:
- Octave value — prioritize grounded workspace data over generic AI content
What ships with it
3 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.
- 10d ago First seen · 349 lines · 50 tokens per session scan A 9de6ac3f7b28
abm is a skill published in the GitHub repository octavehq/lfgtm (11 stars, last pushed 20d ago), licensed MIT. It adds 50 tokens to every session and 3,673 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-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…