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 agentmods add skills/ambient-code/platform/unleash-flagnpx skills add ambient-code/platform --skill unleash-flaggit clone --depth 1 https://github.com/ambient-code/platformWhat 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 | $0.00086 | $0.02498 |
| Opus 5 | $0.00043 | $0.01249 |
| Sonnet 5 | $0.00017 | $0.00500 |
| Haiku 4.5 | $0.00009 | $0.00250 |
Grade A, and why
unleash-flag 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 3d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unleash Feature Flag
Workspace-scoped feature flags for the Ambient Code Platform — naming, gating, evaluation, and lifecycle management.
Checklist
Every new flag requires these steps. Skip none.
- Define the flag in
components/manifests/base/core/flags.json - Gate the frontend using the correct hook for scope
- Update tests to mock the flag hook
- Verify type-check and tests pass
1. Define the Flag
Add to components/manifests/base/core/flags.json:
{
"name": "category.feature-name.enabled",
"description": "Human-readable purpose of this flag",
"tags": [
{
"type": "scope",
"value": "workspace"
}
]
}
Naming Convention
All new flags must use the category.feature-name.enabled format:
category.feature-name.enabled
| Segment | Rules | Examples |
|---|---|---|
category |
One of the standard categories below | runner, model, integration |
feature-name |
Lowercase, hyphen-separated, descriptive | gemini-cli, coderabbit |
.enabled |
Required suffix for all new flags | — |
Standard categories:
| Category | When | Example |
|---|---|---|
integration |
External service integrations | integration.coderabbit.enabled |
runner |
Runner type availability | runner.gemini-cli.enabled |
model |
Model availability (auto-generated by SyncFlags) | model.claude-sonnet-4-5.enabled |
feature |
Platform capabilities | feature.scheduled-export.enabled |
Grandfathered flags (do not rename):
jira-writeldap.autocomplete.enabledscheduled-session.reuse.enabled
These predate the convention. New flags must not follow their patterns.
Rules:
- Unique across the entire system — never reuse a retired flag name
- Descriptive — someone unfamiliar should understand the scope from the name alone
- Dot-delimited with category prefix — enables grouping in workspace settings UI
- Lowercase with hyphens within segments (not underscores, not camelCase)
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.
- 3d ago First seen · 292 lines · 86 tokens per session scan A e960894229e4
unleash-flag is a skill published in the GitHub repository ambient-code/platform (129 stars, last pushed 3d ago), licensed MIT. It adds 86 tokens to every session and 2,498 once invoked, about $0.0004 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
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
extension-creator
Create, scaffold, customize, validate, and locally test Qwen Code extensions. Use when the user wants a new Qwen Code extension, needs help choosing an extension template, wants to add QWEN.md context, commands, skills, agents, MCP servers, settings, hooks, channels, or LSP servers, or asks how to link and test an…
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.
dev-pain-finder
Scrape real developer pain points for any keyword, technology, or problem space from Reddit, Hacker News, dev.to, and GitHub Discussions simultaneously — then group complaints by theme, score them by frequency and upvote weight, and return a ranked opportunity map showing where developer frustration is high and…
argent-native-profiler
Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.