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/speakeasy-api/gram/feature-flagnpx skills add speakeasy-api/gram --skill feature-flaggit clone --depth 1 https://github.com/speakeasy-api/gramWhat 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.01613 |
| Opus 5 | $0.00043 | $0.00807 |
| Sonnet 5 | $0.00017 | $0.00323 |
| Haiku 4.5 | $0.00009 | $0.00161 |
Grade A, and why
feature-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 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 2d ago First seen · 165 lines · 86 tokens per session scan A 1c9cd1bb6304
feature-flag is a skill published in the GitHub repository speakeasy-api/gram (267 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 86 tokens to every session and 1,613 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
installing-caplets
Use when a user wants to install, set up, bootstrap, configure, wire, or troubleshoot Caplets for an agent, MCP client, Pi, OpenCode, Codex, Claude Code, self-hosted remote runtime, or local daemon-first setup.
writing-caplets
Use when creating, updating, reviewing, or validating Caplet files in any project or user environment, including Caplet manifests, agent-facing Caplet bodies, setup/auth metadata, Project Binding declarations, Vault references, runtime requirements, Caplet sets, or install-ready Caplets for private or public use.
caplets
Always use when the user asks to use a capability that may not appear in your visible toolset, or when accessing configured backend capabilities through Caplets, including APIs, CLIs, resources, prompts, backend operations, capability handles, tool schemas, or compact Code Mode CLI results.
aomi-build
Scaffold new Aomi apps and plugins from API docs, OpenAPI/Swagger specs, or SDK references. aomi-build generates production-ready Rust SDK crates (lib.rs, client.rs, tool.rs) with tool schemas, preambles, host-interop flows, and validation — turning a vendor's API surface into AI-agent-callable tools. It covers the…
react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
ossa-agent-authoring
Author and validate OSSA (Open Standard for Software Agents) manifests. Use when creating or editing agent manifests, validating against the OSSA schema, scaffolding new agents, generating agent-card.json, or publishing to a registry. Triggers on tasks involving OSSA YAML/JSON, agent manifests, agent-card, or…