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 agentmods add skills/fmagent-project/fm-agent-plugin/run-incrementalnpx skills add fmagent-project/FM-Agent-Plugin --skill run-incrementalgit clone --depth 1 https://github.com/fmagent-project/FM-Agent-PluginWrote 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/fmagent-project/fm-agent-plugin/run-incremental)<a href="https://agentmods.dev/skills/fmagent-project/fm-agent-plugin/run-incremental"><img src="https://agentmods.dev/badge/skills/fmagent-project/fm-agent-plugin/run-incremental.svg" alt="Measured on agentmods" 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 | $0.00045 | $0.02558 |
| Opus 5 | $0.00023 | $0.01279 |
| Sonnet 5 | $0.00009 | $0.00512 |
| Haiku 4.5 | $0.00005 | $0.00256 |
Grade A, and why
FM-Agent-Run-Incremental 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 4d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute incremental FM-Agent analysis for the current project.
Overview
This skill runs FM-Agent from the plugin data directory $HOME/.fm-agent-plugin/FM-Agent against the current project directory (./) in incremental mode.
Arguments
This skill takes one required argument and one optional argument:
--incremental: run incremental analysis<intent-msg>: optional user-provided intent message describing what changed or what should be analyzed
The skill always generates the intent file from exported summary files written by fm-agent:export. If <intent-msg> is provided, include it at the beginning of the generated intent file.
Rules:
- If
--incrementalis not supplied, stop and tell the user to run/fm-agent:run-incremental --incremental. - If
<intent-msg>is supplied, preserve it as user-provided intent and place it before the exported summaries in the generated intent file. - If multiple extra tokens are supplied after
--incremental, treat all of them together as<intent-msg>.
Invocation Modes
This file defines two explicit procedures:
- Default direct-user mode: the normal
/fm-agent:run-incremental --incremental [<intent-msg>]procedure for direct user invocations. It generates an intent file and launches FM-Agent in the background. - Orchestration mode: a dedicated one-round verification procedure that
fm-agent:auto-fixmust follow when it needs deterministic incremental verification. It runs synchronously.
Mode selection is by entrypoint, not by implicit runtime caller detection:
- Normal
fm-agent:run-incrementalusage follows default direct-user mode. fm-agent:auto-fixmust follow the orchestration mode section when it needs one incremental verification round.
Prerequisites
/fm-agent:installexecuted before to have FM-Agent installed in the plugin data directory$HOME/.fm-agent-plugin/FM-Agent//fm-agent:configexecuted before to set up necessary configurationfm_agent/version.logexists from a prior FM-Agent analysisfm_agent_plugin/export-<short-commit>-summary.mdfiles exist for every commit after the last analyzed commit throughHEAD
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.
- 4d ago First seen · 228 lines · 45 tokens per session scan A 9a23ece155f9
FM-Agent-Run-Incremental is a skill published in the GitHub repository fmagent-project/FM-Agent-Plugin (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 2,558 once invoked, about $0.0002 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
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…