Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/akopichin/afmnpx agentmods add skills/akopichin/afm/afm-pipelinesWrote 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-pipelines)<a href="https://agentmods.dev/skills/akopichin/afm/afm-pipelines"><img src="https://agentmods.dev/badge/skills/akopichin/afm/afm-pipelines/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-pipelines"><img src="https://agentmods.dev/badge/skills/akopichin/afm/afm-pipelines.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.00047 | $0.00942 |
| Opus 5.5 | $0.00019 | $0.00377 |
| Sonnet 5.5 | $0.00009 | $0.00188 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
afm-pipelines 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AFM pipeline setup
The catalog is https://github.com/akopichin/afm-pipelines. AFM ships this skill; the catalog ships packages and the versioned installer. Do not assume the catalog is already cloned, that a suggested pipeline is installed, or that all projects use the same models. Installing a pipeline does not authorize running it.
Find and prepare
Reuse a user-specified catalog checkout. Otherwise clone the catalog into a new cache directory outside the target project, using Git without executing remote shell snippets. Resolve the selected release/ref to an immutable commit and checkout that commit detached. Keep the commit in the installation report. Do not reset an existing checkout with local edits. A local development checkout is allowed when requested; clearly report that it is not a clean published version.
Read the checkout's README and docs/installer.md. For installer protocol 1,
Node.js 22+ and Git are required; install its locked dependency with
npm ci --ignore-scripts --no-audit --no-fund in the catalog checkout.
Run node scripts/pipelines.mjs list, then
node scripts/pipelines.mjs inspect --project /absolute/project/root.
The target must be a Git project root. Inspect manifests and package READMEs to
match the user's objective. Present relevant choices; do not install every
package or invent entries absent from the catalog.
Choose settings
For the selected package, offer the required AFM settings, each role's client, model and reasoning configuration, and optional project-local skills for Claude and/or Codex. Reuse preferences already supplied. Explain package constraints and missing dependencies. The initial installer supports Claude/Codex Docker recipes, including copies of existing compatible AFM profiles. Arbitrary host commands need a separate adapter; do not pretend the Docker recipes work on host.
Use the documented options JSON format. Each role can use its recommended settings, copy an existing profile, or override client/model/reasoning. Copies are isolated by pipeline and role; never edit a shared profile to customize just one pipeline. Package recommendations are not mandatory model identities.
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 First seen · 87 lines · 47 tokens per session scan A 115e844de1d2
afm-pipelines is a skill published in the GitHub repository akopichin/afm (25 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 942 once invoked, about $0.0002 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-10-27.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.