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 ashish7802/awesome-api-skills --skill unkeygit clone --depth 1 https://github.com/ashish7802/awesome-api-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/ashish7802/awesome-api-skills/unkey)<a href="https://agentmods.dev/skills/ashish7802/awesome-api-skills/unkey"><img src="https://agentmods.dev/badge/skills/ashish7802/awesome-api-skills/unkey/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ashish7802/awesome-api-skills/unkey"><img src="https://agentmods.dev/badge/skills/ashish7802/awesome-api-skills/unkey.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00491 |
| Opus 5 | $0.00000 | $0.00246 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
unkey 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.
What it actually says
Unkey API Key & Rate Limiting Skill
Overview
Unkey is high-performance infrastructure for minting, revoking, validating API keys, and enforcing distributed rate limits at the edge with global sub-10ms response times.
Installation
npm install @unkey/api @unkey/ratelimit
Verifying an Inbound API Key
import { verifyKey } from '@unkey/api';
export async function authenticateApiKey(apiKeyValue: string) {
const { result, error } = await verifyKey({
key: apiKeyValue,
apiId: process.env.UNKEY_API_ID!,
});
if (error) {
console.error('Unkey verification failed:', error);
return { authenticated: false };
}
if (!result.valid) {
return { authenticated: false, reason: result.code };
}
return {
authenticated: true,
ownerId: result.ownerId,
meta: result.meta,
};
}
Creating a New Customer API Key
import { Unkey } from '@unkey/api';
const unkey = new Unkey({ rootKey: process.env.UNKEY_ROOT_KEY! });
const created = await unkey.keys.create({
apiId: process.env.UNKEY_API_ID!,
prefix: 'acme',
ownerId: 'user_9921',
name: 'Production Worker Key',
ratelimit: {
type: 'fast',
limit: 100,
duration: 60000, // 100 requests per minute
},
meta: {
tier: 'enterprise',
},
});
console.log('Customer API Key:', created.result?.key);
AI Pitfalls & Anti-Hallucination Guidelines
- Plaintext Key Security: The plaintext API key is only returned once upon creation. Store hash or instruct user to copy immediately.
- Root Key vs Client Verification: Key creation requires
UNKEY_ROOT_KEY. Verification only requiresapiId.
Production Verification Checklist
- API keys verified on edge runtime before handler execution
- Rate limit exhaustion returns HTTP 429 Too Many Requests
- Key prefixes utilized to simplify customer debugging (e.g.
pk_live_...)
Last Verified: 2026-07-03
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 · 73 lines · 0 tokens per session scan A 176e0391152b
unkey is a skill published in the GitHub repository ashish7802/awesome-api-skills (13 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 491 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-09-10.
Other skills, from other repositories
composio
Build AI agents and apps with Composio - access 200+ external tools with Tool Router or direct execution.
analyzing-api-gateway-access-logs
Parses API Gateway access logs (AWS API Gateway, Kong, Nginx) to detect BOLA/IDOR attacks, rate limit bypass, credential scanning, and injection attempts. Uses pandas for statistical analysis of request patterns and anomaly detection. Use when investigating API abuse or building API-specific threat detection rules.
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.
testing-integration
Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation. Use when testing API boundaries, verifying contracts, or validating cross-service integration.
presentation
Turn a tech-spec directory into an interactive, marketing-grade web presentation — built so engineers understand the design, the reader is convinced of the why, and the result is shareable in public. Use when someone wants a spec turned into a deck.
iii-core-primitives
Use when registering iii functions, binding triggers, selecting sync/void/enqueue invocation, creating workers, inspecting the live worker registry, installing registry workers, authoring custom triggers, moving channel data, or adapting external HTTP functions across TypeScript, Python, and Rust.