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 inngestgit 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/inngest)<a href="https://agentmods.dev/skills/ashish7802/awesome-api-skills/inngest"><img src="https://agentmods.dev/badge/skills/ashish7802/awesome-api-skills/inngest/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/inngest"><img src="https://agentmods.dev/badge/skills/ashish7802/awesome-api-skills/inngest.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.00549 |
| Opus 5 | $0.00000 | $0.00275 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
inngest 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inngest API Skill
Overview
Inngest is a developer-first platform for writing durable background jobs, scheduled tasks, and complex multi-step workflows directly in your codebase.
Installation
npm install inngest
Client & Workflow Definition
import { Inngest } from 'inngest';
export const inngest = new Inngest({ id: 'my-saas-app' });
// Define a multi-step durable workflow
export const onboardUserWorkflow = inngest.createFunction(
{ id: 'onboard-user', retries: 3 },
{ event: 'app/user.signup' },
async ({ event, step }) => {
// Step 1: Create Stripe customer
const customer = await step.run('create-stripe-customer', async () => {
return { customerId: 'cus_123', email: event.data.email };
});
// Step 2: Sleep for 3 days without keeping server active
await step.sleep('wait-for-trial', '3 days');
// Step 3: Send check-in email
await step.run('send-checkin-email', async () => {
console.log('Sending follow up email to', customer.email);
return { sent: true };
});
return { completed: true };
}
);
Next.js / Framework Route Setup
// app/api/inngest/route.ts
import { serve } from 'inngest/next';
import { inngest, onboardUserWorkflow } from '@/lib/inngest';
export const { GET, POST, PUT } = serve({
client: inngest,
functions: [onboardUserWorkflow],
});
Sending Events
await inngest.send({
name: 'app/user.signup',
data: {
userId: 'usr_456',
email: '[email protected]',
},
});
AI Pitfalls & Anti-Hallucination Guidelines
- Step Code Execution: Inngest re-executes function code between steps to memoize results. Code outside
step.run()will run multiple times. Put all side-effects insidestep.run(). - Serialization: Return values from
step.run()must be JSON-serializable (no raw socket handles or circular references).
Production Verification Checklist
-
serve()endpoint is publicly reachable or routed via Inngest Dev Server - Side-effects wrapped inside
step.run() - Concurrency and rate limit keys configured for external API calls
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 · 75 lines · 0 tokens per session scan A 6d800be0d2d9
inngest 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 549 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.