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 skills add Jamie-BitFlight/claude_skills --skill api-stategit clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jamie-bitflight/claude_skills/api-state)<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/api-state"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/api-state.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00057 | $0.00931 |
| Opus 5 | $0.00028 | $0.00465 |
| Sonnet 5 | $0.00011 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
api-state 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API State
One research angle in a multi-angle technical research system. Singular focus: current API syntax, changelog, and breaking changes for a specific library or protocol version.
Runs independently. No shared state with other research angles during execution. Return all findings as content — do not write to any backlog item.
Workflow
Step 1 — Scope
Research target received from orchestrator:
$ARGUMENTS
Confirm the technology name, version, and specific API surface before proceeding. If any are missing or ambiguous, state the gap and output:
STATUS: BLOCKED Reason: [missing field] — cannot proceed without [technology name | version | API surface].
Step 2 — Current API State
Fetch the primary documentation page for the technology. Use mcp__Ref__ref_search_documentation
to locate the canonical docs URL, then mcp__Ref__ref_read_url to retrieve the page. If the
library is not indexed by Ref, use context7 (mcp__context7__resolve-library-id then
mcp__context7__query-docs). Derive the URL from the confirmed scope — do not rely on training
data for the URL or for version-specific syntax.
Extract and record:
- Exact method/class/decorator signatures
- All parameter forms (required, optional, typed, variadic)
- Return types and async behaviour
- Context injection patterns (if applicable to the technology)
- Any configuration or initialization requirements
Cite each item with the source URL and access date.
Step 3 — Changelog
Fetch the raw changelog. Locate it at the canonical path for the technology — commonly
CHANGELOG.md or CHANGES.md in the GitHub repository, or the GitHub Releases page. Use
mcp__Ref__ref_read_url for the changelog URL. Fall back to WebFetch for raw GitHub
URLs not served by Ref.
Extract all entries relevant to the API surface confirmed in Step 1, version by version. Cite each entry with its version number and source URL.
If the changelog is absent or the relevant entries are not present, state this explicitly: "Changelog not found at [URLs attempted]" or "No changelog entries for [API surface] found in versions [range searched]."
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 · 114 lines · 57 tokens per session scan A 643660179422
api-state is a skill published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 931 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.