rugged-gemini: Skill for Claude Code

.gemini/skills/feature-flags-principles/SKILL.md

feature-flags-principles is a skill for Claude Code, Gemini CLI from irahardianto/rugged-gemini. It costs 34 tokens per session (701 once invoked), scanned A, original, MIT.

Guidance for using feature flags, which are switches that change software behavior without changing the deployed code. It covers when flags are justified, how to evaluate them, and how to test and retire them.

In plain words
What is it for?
Use it when a product or architecture requires gradual releases, A/B tests, emergency switches, or tier-based access, including choosing an evaluation approach and testing flag combinations.
Why use it?
It helps prevent unnecessary flag complexity and makes rollout, kill-switch, experiment, and access-control decisions explicit. It also highlights where flag checks and their storage should be defined.

Skill for Claude CodeGemini CLI

Written for Claude Code and Gemini CLI: user-invocable in frontmatter, but also installed under .gemini/. Also seen: mentions Gemini CLI.

This is irahardianto/rugged-gemini's own configuration. It tells Claude Code and Gemini CLI how to work on rugged-gemini itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything rugged-gemini configures →

Reuse

Borrowing it

Nothing to install: this file belongs to irahardianto/rugged-gemini. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/irahardianto/rugged-gemini/main/.gemini/skills/feature-flags-principles/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/irahardianto/rugged-gemini

Made for: Claude Code, Gemini CLI.

Wrote 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.

agentmods badge for feature-flags-principles

README.md
[![agentmods](https://agentmods.dev/badge/skills/irahardianto/rugged-gemini/feature-flags-principles/github.svg)](https://agentmods.dev/skills/irahardianto/rugged-gemini/feature-flags-principles)
Your own site
<a href="https://agentmods.dev/skills/irahardianto/rugged-gemini/feature-flags-principles"><img src="https://agentmods.dev/badge/skills/irahardianto/rugged-gemini/feature-flags-principles/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.

agentmods 80×15 button for feature-flags-principles

Your own site · 80×15
<a href="https://agentmods.dev/skills/irahardianto/rugged-gemini/feature-flags-principles"><img src="https://agentmods.dev/badge/skills/irahardianto/rugged-gemini/feature-flags-principles.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 701 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00701
Opus 5 $0.00017 $0.00351
Sonnet 5 $0.00007 $0.00140
Haiku 4.5 $0.00003 $0.00070

Measured 9d ago against content hash 71dfe22d94e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

feature-flags-principles 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 9d 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.

.gemini/skills/feature-flags-principles/SKILL.md · 87 lines

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.

Feature Flags Principles

CAUTION: Do NOT implement unless PRD/arch explicitly requires: gradual rollout, A/B testing, kill switches, or tier gating. Flags add real complexity (evaluation infra, lifecycle, test permutations). No spec → deploy directly.

When to Use

Use Case Type Example
Gradual rollout Release new-checkout: 0→5→25→100%
Kill switch Ops use-legacy-payment
A/B test Experiment button-color-test
Tier gating Permission pro-tier-analytics

Infrastructure

Flag backend MUST be specified in tech arch doc. Do NOT choose independently — ask user.

Approach When Notes
Managed SaaS Teams >5, multi-env LaunchDarkly, Flagsmith, Unleash
Self-hosted Full control Unleash/Flagsmith OSS
Firebase Remote Config Mobile + Firebase Firebase SDK
Static (YAML/env) Solo, simple on/off Startup load, no runtime targeting

Evaluation Rules

  • Server-side for security-sensitive (never trust client)
  • Evaluate at request boundary — never inside pure business logic
  • Default disabled (fail closed if service unreachable)
  • Wrap flag checks once (service method/middleware, not scattered)
// ✅ Flag at boundary
func (s *Service) CreateOrder(ctx context.Context, req Request) (Response, error) {
    useNewPricing := s.flags.IsEnabled(ctx, "new-pricing-engine", req.UserID)
    if useNewPricing {
        return s.handleWithNewPricing(ctx, req)
    }
    return s.handleWithLegacyPricing(ctx, req)
}

// ❌ Flag inside business logic
func calculateDiscount(items []Item) float64 {
    if flags.IsEnabled("new-discount-rules") { ... }   // NO
}

Lifecycle

Flags are temporary. Debt accumulates fast.

  • Every flag has an owner
  • Release flags: max 90 days
  • 100% rollout → create removal ticket immediately
  • Ops flags can be permanent (documented)
  • Experiment flags removed when concluded
  • Review flags in sprint planning

Testing

  • Unit: test each branch independently (on + off)
  • Integration: default to production-expected state
  • Do NOT enumerate all flag combinations
  • Use test-only override (flags.Override(ctx, "flag", true))

Read the full file on GitHub · 87 lines

Changes

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.

  1. 9d ago First seen · 87 lines · 34 tokens per session scan A 71dfe22d94e4

Subscribe to this mod's changes

feature-flags-principles is a skill published in the GitHub repository irahardianto/rugged-gemini (5 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 701 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens