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/discovernpx skills add ambient-code/platform --skill discovergit 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.00064 | $0.00693 |
| Opus 5 | $0.00032 | $0.00347 |
| Sonnet 5 | $0.00013 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade B, and why
discover scanned grade B with 1 finding 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls .claude/skills/ 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discover Domain Skills
Before writing or changing anything, discover what skills and context are available for the domains you're about to work in.
When to Use
Every time. This skill is the entry point for all coding and spec work. Do not skip it, even for one-line fixes.
User Input
$ARGUMENTS
If provided, use the input to narrow which domains to check. Otherwise, infer from the task context.
Steps
1. Identify Relevant Domains
Map the work to one or more capability domains:
| Domain | When working on |
|---|---|
sessions |
Session lifecycle, data model, API resources, messages, events |
control-plane |
Operator, reconciliation, scheduling, runner provisioning |
agents |
Agent model, runner, runtime registry, prompts |
integrations |
MCP server, Gerrit, external services, feature flags |
frontend |
UI components, pages, React Query hooks |
auth |
OAuth, credentials, RBAC, tokens |
projects |
Project management, settings, workspaces |
cli |
TUI, acpctl commands |
specs |
specs |
If unsure, check which specs/ subdirectories exist:
ls -d specs/*/
2. Visit Each Domain
For every relevant domain, cd into its spec directory and list available skills:
cd specs/{domain}
ls .claude/skills/ 2>/dev/null
ls skills/ 2>/dev/null
Read the SKILL.md of any discovered skill that looks relevant to the task at hand.
3. Load Domain Specs
While in the domain directory, check for specs that describe the desired state of what you're about to change:
ls *.spec.md 2>/dev/null
Read the relevant spec before implementing — code reconciles against specs, not the other way around.
4. Check Deployment Skills
If the work involves deployment, manifests, Docker builds, or cluster operations, check for deployment skills:
ls skills/deployments/ 2>/dev/null
Read the relevant SKILL.md — these contain environment config, prerequisites, and troubleshooting for deploying each component.
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.
- 2d ago First seen · 105 lines · 64 tokens per session scan B 4ea51c3a6f28
discover is a skill published in the GitHub repository ambient-code/platform (129 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 693 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
powerpoint
Create designed, editable PowerPoint .pptx presentations with PptxGenJS. Use when the user asks to create, generate, update, or inspect a deck, slide deck, presentation, or .pptx file.
argent-tv-interact
Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it.
company-hiring-intelligence
Reverse-engineer what a company is building by scraping their job postings, careers page, LinkedIn Jobs, and engineering blog using TinyFish web agents. Use whenever a user wants to understand a company's strategic direction from hiring signals, do competitive intelligence, figure out a tech stack from job…
aidd-dev:08:for-sure
Iterative agent loop that tracks attempts and retries until a success condition is met. Use when the user says "for sure", "make sure", "keep trying until", "loop until done", "don't stop until", or needs guaranteed completion of a task with explicit success criteria.