triage-feature-flags

An issue and pull-request classifier for finding work related to feature flags, user cohorts, and early-access features. It is used by an issue-triage command.

In plain words
What is it for?
Use it to sort internal or external GitHub issues and pull requests into the Feature Flags team’s queue.
Why use it?
It reduces the manual work of checking GitHub issues and code changes to decide whether the Feature Flags team should handle them.

Agent

Install

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.

agentmods
npx agentmods add agents/haacked/dotfiles/triage-feature-flags
Clone the repo
git clone --depth 1 https://github.com/haacked/dotfiles
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,137 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00047 $0.01137
Opus 5 $0.00023 $0.00568
Sonnet 5 $0.00009 $0.00227
Haiku 4.5 $0.00005 $0.00114

Measured 2d ago against content hash 8d303483db2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

triage-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 2d 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.

ai/agents/triage-feature-flags.md · 87 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 87 lines · 47 tokens per session scan A 8d303483db2a

Subscribe to this mod's changes

triage-feature-flags is an agent published in the GitHub repository haacked/dotfiles (131 stars, last pushed 4d ago), with no licence file. It adds 47 tokens to every session and 1,137 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-30.