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 harness/harness-skills --skill fme-pipelinegit clone --depth 1 https://github.com/harness/harness-skillsWrote 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/harness/harness-skills/fme-pipeline)<a href="https://agentmods.dev/skills/harness/harness-skills/fme-pipeline"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/fme-pipeline/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/harness/harness-skills/fme-pipeline"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/fme-pipeline.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.00147 | $0.03776 |
| Opus 5.5 | $0.00059 | $0.01510 |
| Sonnet 5.5 | $0.00029 | $0.00755 |
| Haiku 4.5 | $0.00015 | $0.00378 |
Grade A, and why
fme-pipeline 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 yesterday.
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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FME Pipeline
Compose Harness pipelines with FmeFlag* / FmeSegment* steps for flag rollout scenarios. Generates tailored pipelines — progressive ramp, multi-environment promotion, beta cohorts, config promotion, bootstrap, retirement, segment sync, and test targeting — rather than a single fixed template.
Related: Direct flag operations → /update-flag-targeting. Experiments → /manage-experiments, /review-experiment-results. Flag creation → /create-feature-flag. Lifecycle → /manage-flag-lifecycle. Segments → /manage-segments. State → /explain-flag. Discovery → /discover-feature-flags. Code removal → /cleanup-feature-flags. Running → /run-pipeline. Triggers → /create-trigger.
Tools
Works through the Harness MCP server or the Harness CLI; names are from tool-map.md.
| Operation | MCP | CLI |
|---|---|---|
| List environments | harness_list · fme_environment · compact: false |
harness list fme_environment --json |
| Get flag | harness_get · fme_feature_flag · params: { feature_flag_name } |
harness get feature_flag <name> --json |
| List definitions | harness_list · fme_feature_flag_definition · params: { feature_flag_name } · filters: { offset: 0, limit: 100 } · compact: false |
harness list feature_flag:definition <name> --json |
| List rollout statuses | harness_list · fme_rollout_status · compact: false |
harness list rollout_status --json |
| List experiments | harness_list · fme_experiment · filters: { parent_type: "FEATURE_FLAG", parent_name, status: ["ACTIVE", "PAUSED"] } · compact: false |
harness list experiment --parent-type FEATURE_FLAG --parent-name <flag> --status ACTIVE --json, then again with --status PAUSED |
| List user groups | harness_list · user_group |
harness list user_group --json |
| List connectors | harness_list · connector |
harness list connector --json |
| Get project | harness_list · project · org_id |
harness list project --org <org> --json |
| Get pipeline | harness_get · pipeline · params: { pipeline_id } · org_id · project_id |
harness get pipeline <id> --org <org> --project <proj> --json |
| Create pipeline | harness_create · pipeline · org_id · project_id · body: { yamlPipeline } |
harness create pipeline -f pipeline.yaml --org <org> --project <proj> |
| Update pipeline | harness_update · pipeline · params: { pipeline_id } · org_id · project_id · body: { yamlPipeline } |
harness update pipeline <id> -f pipeline.yaml --org <org> --project <proj> |
What ships with it
12 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.
- references/blueprints.md 4.9 KB
- references/blueprints/l1-flag-bootstrap.yaml 4.0 KB
- references/blueprints/l2-flag-retirement.yaml 2.4 KB
- references/blueprints/l3-segment-sync.yaml 1.8 KB
- references/blueprints/l4-test-targeting.yaml 2.0 KB
- references/blueprints/r1-progressive-ramp.yaml 7.0 KB
- references/blueprints/r2-multi-env-promotion.yaml 28 KB
- references/blueprints/r3-beta-cohort.yaml 8.6 KB
- references/blueprints/r4-config-promotion.yaml 2.4 KB
- references/building-blocks.md 8.9 KB
- references/scenarios.md 16 KB
- references/step-catalog.md 20 KB
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.
- yesterday Changed · +1 lines 55ae659d5ca9
- 9d ago First seen · 148 lines · 147 tokens per session scan A 917b025e8997
fme-pipeline is a skill published in the GitHub repository harness/harness-skills (117 stars, last pushed yesterday), licensed Apache-2.0. It adds 147 tokens to every session and 3,776 once invoked, about $0.0006 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-07.
Other skills, from other repositories
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
google-agents-cli-scaffold
This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or "upgrade my project". Part of the agents-cli skills suite. Covers agents-cli scaffold create, scaffold enhance, and…
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
babysit
Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.
azure-kubernetes-app-deploy
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster…
deploying-to-staging-environment
Use when deploying changes to staging across relay, relay-dashboard, and relay-cloud repos - coordinates multi-repo branch syncing using git worktrees, automatically triggers staging deployments via GitHub Actions.