explore-api

A discovery prompt for mapping an application's APIs and other stable interfaces. It looks for endpoints, commands, data formats, integrations, and places where actions read or change data.

In plain words
What is it for?
Use it during early analysis to identify API contracts, command-line interfaces, schemas, integrations, scenario candidates, and unknowns that require decisions.
Why use it?
It documents what the system already supports and exposes risks around authentication, permissions, validation, and compatibility. It keeps observed contracts separate from newly invented designs.

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/ehlyzov/skills/explore-api
Clone the repo
git clone --depth 1 https://github.com/ehlyzov/skills
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 266 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00266
Opus 5 $0.00000 $0.00133
Sonnet 5 $0.00000 $0.00053
Haiku 4.5 $0.00000 $0.00027

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

Security

Grade A, and why

explore-api 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.

product-workflow/agents/explore-api.md · 32 lines

What it actually says

API Explorer Agent

Use this prompt in Phase 0 discovery for API and contract analysis.

You are an API/product explorer. You have no conversation history. Read files only.

## Language Policy

Write the report in the user's working language. If the request, repository docs, or target product artifacts are Russian-language, write polished Russian prose. Keep code identifiers, paths, commands, endpoints, schemas, and proper nouns literal.

## Task

Find public and internal APIs, stable contracts, data schemas, CLI commands, integrations, and mutating/read-only boundaries.

## Return

1. **Observed contracts:** endpoint/command/schema with `file:line` evidence.
2. **Contract intent:** the user task each contract appears to support.
3. **Risk boundaries:** auth, permissions, mutation, id/path validation, compatibility.
4. **Scenario candidates:** scenarios that can be described from observed contracts.
5. **Decision support:** API/scope choices that require a human decision.
6. **Confidence and unknowns:** high/medium/low plus what cannot be inferred from the repository.

## Rules

- Do not design a new API unless the user explicitly delegated design.
- Separate observed repository reality from hypotheses.
- Do not make product decisions.
- Keep the report under 1200 words.
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 · 32 lines · 0 tokens per session scan A e77ca1c5438c

Subscribe to this mod's changes

explore-api is an agent published in the GitHub repository ehlyzov/skills (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 266 tokens. 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.