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 akopichin/afm --skill afm-initgit clone --depth 1 https://github.com/akopichin/afmWrote 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/akopichin/afm/afm-init)<a href="https://agentmods.dev/skills/akopichin/afm/afm-init"><img src="https://agentmods.dev/badge/skills/akopichin/afm/afm-init/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/akopichin/afm/afm-init"><img src="https://agentmods.dev/badge/skills/akopichin/afm/afm-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.00237 |
| Opus 5.5 | $0.00004 | $0.00095 |
| Sonnet 5.5 | $0.00002 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
afm-init 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 3d 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
afm init — Create a Flow
Step 0: Verify Installation
which afm
Step 1: Gather Information
If the user wants a ready-made workflow, check the AFM pipeline catalog through
the bundled afm-pipelines skill before designing a new flow. Offer a matching
package when one exists. Continue with a custom flow when that is the user's
preference or no package fits; catalog access is not required for custom flows.
Use AskUserQuestion to collect:
- Flow name (kebab-case)
- Flow description
- For each stage: id, name, description, depends_on, agents
Step 2: Run Init
Pass the answers interactively to:
afm init
Or construct the YAML manually and save to .afm/flows/{name}.yaml.
Step 3: Confirm
Show the created file path and contents. Ask if user wants to run it now.
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.
- 3d ago Changed · +5 lines 8a8a4530e778
- 7d ago Changed · +1 lines · +4 tokens per session c55cc3da7dd6
- 2mo ago First seen · 34 lines · 7 tokens per session scan A 537aee56455f
afm-init is a skill published in the GitHub repository akopichin/afm (25 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 237 once invoked, about $0.0000 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.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…