Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
npm install -g @steipete/inngestTaken from the project's README on GitHub.
None of the 42 rules matched — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against 42 published rules built on the SlowMist agent-security taxonomy, refreshed every 8 hours.
The quality score combines nine heuristic checks of the repo and its README: completeness, clarity, specificity, examples, structure, agent readiness, step-by-step content, instruction quality and security notes. It rates how well the project explains itself to an agent, not the code.
| Stars | 81 |
| Forks | 6 |
| Language | TypeScript |
| Category | AI Tool |
| License | MIT |
| Quality Score | 65/100 |
| Open Issues | 2 |
| Last Updated | 2026-10-30 |
| Created | 2025-09-12 |
| Platforms | cli, node |
| Est. Tokens | ~17k |
Inngest CLI A powerful CLI for managing Inngest jobs with support for watching, canceling, and filtering by status. Features Query run status by run ID or event ID with detailed output List runs with filtering by status, function, and pagination support Watch runs in real-time with configurable polling intervals and timeouts Cancel runs individually or in bulk with conditional expressions and...
Looking for a inngest alternative? If you're comparing inngest with other ai tool tools, these 3 projects are the closest alternatives on Agent Skills Hub — ranked by topic overlap, star count, and community traction.
Skip to content github / docs Code Issues 80 Pull requests 35 Discussions Actions Projects 2 Security Insights
Skill to talk to Claude about your projects over the phone
.NET MAUI skills for GitHub Copilot and Claude Code
Explore other popular ai tool tools:
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy: 42 published rules, covering credential harvesting, data exfiltration, curl | sh installers and more. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: