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 manage-segmentsgit 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/manage-segments)<a href="https://agentmods.dev/skills/harness/harness-skills/manage-segments"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/manage-segments/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/manage-segments"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/manage-segments.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.00155 | $0.03643 |
| Opus 5.5 | $0.00062 | $0.01457 |
| Sonnet 5.5 | $0.00031 | $0.00729 |
| Haiku 4.5 | $0.00015 | $0.00364 |
Grade A, and why
manage-segments 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Segments
Manage metadata for STANDARD, LARGE, and RULE_BASED segments, STANDARD membership, and approved RULE_BASED editor changes. Every mutation requires a complete reference-impact check and explicit approval. LARGE bulk membership operations are outside this skill's scope.
Tools
Works through Harness MCP or CLI with equivalent scope, confirmation and verification requirements. Discover exact CLI action syntax through command help; use tool-map.md for mappings. STANDARD in metadata examples stands for the selected type; definition/key rows apply only to STANDARD.
| Operation | MCP | CLI |
|---|---|---|
| List traffic types | harness_list · fme_traffic_type · compact: false |
harness list traffic_type --json |
| List environments | harness_list · fme_environment · compact: false |
harness list fme_environment --json |
| List flags | harness_list · fme_feature_flag · size: 50 · compact: false |
harness list feature_flag --json --limit 50 |
| List experiments | harness_list · fme_experiment · filters: { parent_type: "FEATURE_FLAG", parent_name, environment_id, status: ["ACTIVE", "PAUSED"], offset: 0, limit: 100 } · compact: false |
harness list experiment --parent-type FEATURE_FLAG --parent-name <flag> --env <env-id> --status ACTIVE --json, then PAUSED; fully paginate both |
| List flag definitions | harness_list · fme_feature_flag_definition · params: { feature_flag_name } · filters: { offset: 0, limit: 100 } · compact: false |
harness list feature_flag:definition <flag> --json |
| List segments | harness_list · fme_segment · filters: { segment_type, status?, offset: 0, limit: 100 } · compact: false |
harness list segment --segment-type STANDARD --json; safety gates list ACTIVE and ARCHIVED using declared status filters |
| Get segment | harness_get · fme_segment · params: { segment_name, segment_type } |
harness get segment <name> --segment-type STANDARD --json |
| Create segment | harness_create · fme_segment · body: { name, trafficType, segmentType, description?, tags?, owners? } |
harness create segment <name> --traffic-type user --segment-type STANDARD |
| Update segment | harness_update · fme_segment · params: { segment_name, segment_type } · body: { description?, tags?, owners? } |
harness update segment <name> --segment-type STANDARD --set description=foo |
| Delete segment | harness_delete · fme_segment · params: { segment_name, segment_type } |
harness delete segment <name> --segment-type STANDARD |
| List definitions | harness_list · fme_segment_definition · filters: { environment_id, status?, offset: 0, limit: 100 } · compact: false |
harness list segment:definition --env <env-id> --json |
| Get definition | harness_get · fme_segment_definition · params: { segment_name, environment_id } |
harness get segment:definition <name> --env <env-id> --json |
| Create definition | harness_create · fme_segment_definition · params: { segment_name, environment_id } · body: { description? }? |
harness create segment:definition <name> --env <env-id> |
| Update definition | harness_update · fme_segment_definition · params: { segment_name, environment_id } · body: { description? } |
harness update segment:definition <name> --env <env-id> --set description=foo |
| Delete definition | harness_delete · fme_segment_definition · params: { segment_name, environment_id } |
harness delete segment:definition <name> --env <env-id> |
| List keys | harness_execute · fme_segment_definition · action="list_keys" · params: { segment_name, environment_id, offset?, limit? } |
Discover the key-list action and pagination arguments through CLI help |
| Add keys | harness_execute · fme_segment_definition · action="add_keys" · params: { segment_name, environment_id, replace? } · body: { keys, comment?, title? } |
Discover the key-add action and replacement argument through CLI help |
| Remove keys | harness_execute · fme_segment_definition · action="remove_keys" · params: { segment_name, environment_id } · body: { keys, comment?, title? } |
Discover the key-remove action through CLI help |
What ships with it
1 file 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.
- yesterday Changed · +1 lines 6dd2000408c5
- 9d ago First seen · 168 lines · 155 tokens per session scan A 5f58eae253cc
manage-segments is a skill published in the GitHub repository harness/harness-skills (117 stars, last pushed yesterday), licensed Apache-2.0. It adds 155 tokens to every session and 3,643 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
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
haiku
When writing a haiku for this bot, follow these conventions.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".