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-flag-lifecyclegit 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-flag-lifecycle)<a href="https://agentmods.dev/skills/harness/harness-skills/manage-flag-lifecycle"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/manage-flag-lifecycle/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-flag-lifecycle"><img src="https://agentmods.dev/badge/skills/harness/harness-skills/manage-flag-lifecycle.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.00181 | $0.03116 |
| Opus 5.5 | $0.00072 | $0.01246 |
| Sonnet 5.5 | $0.00036 | $0.00623 |
| Haiku 4.5 | $0.00018 | $0.00312 |
Grade A, and why
manage-flag-lifecycle 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Flag Lifecycle
Manage metadata, archive readiness, archive/unarchive, and deletion for Harness FME feature flags. Related: update-flag-targeting (targeting), discover-feature-flags (stale flags), cleanup-feature-flags (code removal).
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 |
| List flags | harness_list · fme_feature_flag · size: 50 · filters: { name?, tags?, rollout_status_id?, offset? } · compact: false |
harness list feature_flag --search <name> --status <ACTIVE|ARCHIVED> --json (CLI has no --tags/--rollout-status-id; filter client-side on the full JSON, which MCP's tags/rollout_status_id filters do server-side) |
| Get flag | harness_get · fme_feature_flag · params.feature_flag_name |
harness get feature_flag <name> --json |
| Update flag | harness_update · fme_feature_flag · params.feature_flag_name · body: { description?, tags?, owners?, rolloutStatus? } |
harness update feature_flag <name> --set description="..." --set rollout_status=<uuid> (CLI field id is rollout_status; --set rolloutStatus.id= doesn't match the spec's mutable field id and fails) |
| List definitions | harness_list · fme_feature_flag_definition · params.feature_flag_name · filters: { offset: 0, limit: 100 } (advance offset through every page) · compact: false |
harness list feature_flag:definition <flag> --json |
| Get definition | harness_get · fme_feature_flag_definition · params: { feature_flag_name, environment_id } |
harness get feature_flag:definition <flag> --env <env-id> --json |
| Delete definition | harness_delete · fme_feature_flag_definition · params: { feature_flag_name, environment_id } |
harness delete feature_flag:definition <flag> --env <env-id> |
| Archive flag | harness_execute · fme_feature_flag · action="archive" · params.feature_flag_name · body: { comment?, title? } |
harness execute feature_flag:archive <name> --comment "..." --title "..." |
| Unarchive flag | harness_execute · fme_feature_flag · action="unarchive" · params.feature_flag_name · body: { comment?, title? } |
harness execute feature_flag:unarchive <name> --comment "..." |
| Delete flag | harness_delete · fme_feature_flag · params.feature_flag_name |
harness delete feature_flag <name> |
| List experiments | harness_list · fme_experiment · filters: { parent_type: "FEATURE_FLAG", parent_name, environment_id?, status: ["ACTIVE", "PAUSED"], offset: 0, limit: 100 } (apply pagination completeness checks) · compact: false |
harness list experiment --parent-type FEATURE_FLAG --parent-name <name> --status ACTIVE --json, then again with --status PAUSED |
| List rollout statuses | harness_list · fme_rollout_status · compact: false |
harness list rollout_status --json |
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 f9a38fc102cb
- 9d ago First seen · 149 lines · 181 tokens per session scan A 0b1a7e6e6c4c
manage-flag-lifecycle is a skill published in the GitHub repository harness/harness-skills (117 stars, last pushed yesterday), licensed Apache-2.0. It adds 181 tokens to every session and 3,116 once invoked, about $0.0007 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".