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 dungnotnull/hybrid-harness-chaos-process-prm --skill s08-feature-flagsgit clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prmWrote 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/dungnotnull/hybrid-harness-chaos-process-prm/s08-feature-flags)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s08-feature-flags"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s08-feature-flags/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/dungnotnull/hybrid-harness-chaos-process-prm/s08-feature-flags"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s08-feature-flags.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.00104 | $0.02625 |
| Opus 5 | $0.00052 | $0.01313 |
| Sonnet 5 | $0.00021 | $0.00525 |
| Haiku 4.5 | $0.00010 | $0.00263 |
Grade A, and why
harness-feature-flags 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 12d 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 — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Feature Flags
Purpose
Implement feature flags as first-class delivery primitives — decoupling code deployment from feature release, enabling instant rollbacks without redeployment, and supporting data-driven percentage rollouts.
Input Contract
| Input | Source | Required |
|---|---|---|
| Service definitions | s05 (workflow_context.artifacts) | Yes |
| PRD feature requirements | s01 context | Yes |
| Blast radius control requirements | s14 output | No |
| Chaos flag gating needs | s12 experiment context | No |
| SDK language preference | s02 taste | No |
Output Contract
| Output | Destination | Format |
|---|---|---|
| Feature flag YAML definitions | .commandcode/artifacts/feature-flags.yaml |
YAML |
| SDK integration code snippets | s11 (testing), service teams | Code |
| Flag pipeline YAML | .commandcode/artifacts/flag-pipeline.yaml |
YAML |
| Kill switch configurations | .commandcode/artifacts/kill-switches.yaml |
YAML |
| Flag cleanup schedule | s03 (tracker for dates) | Markdown checklist |
| Chaos gate flags | s14 (blast radius), s21 (alerts) | YAML |
Prerequisites
- Harness FF module enabled on account
- Target runtime: browser / server / mobile (determines SDK)
- Flag naming convention agreed (see below)
- Monitoring dashboards ready to track flag impact
Flag Taxonomy
| Flag Type | Use Case | Example |
|---|---|---|
| Release flag | New feature gating | FF_PAYMENT_NEW_CHECKOUT |
| Ops flag | Kill switch / incident | FF_OPS_DISABLE_RECOMMENDATIONS |
| Experiment flag | A/B test | FF_EXP_HOMEPAGE_HERO_V2 |
| Permission flag | Role-based access | FF_PERM_ADMIN_BULK_DELETE |
| Chaos flag | Gate fault injection | FF_CHAOS_PAYMENT_POD_DELETE |
Naming convention: FF_<TYPE>_<DOMAIN>_<FEATURE> in SCREAMING_SNAKE_CASE
Flag Lifecycle
Create (OFF) → Test (internal targets) → Staged rollout (%)
→ 100% ON → Cleanup (remove from code + FF platform)
Flags are technical debt. Every flag must have a cleanup date set at creation time.
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.
- 12d ago First seen · 419 lines · 104 tokens per session scan A 0595a02a6e9e
harness-feature-flags is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 104 tokens to every session and 2,625 once invoked, about $0.0005 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…