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 agentmods add agents/crypticsaiyan/githubwrapped/motia-developergit clone --depth 1 https://github.com/crypticsaiyan/githubwrappedWhat 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 | $0.00032 | $0.00904 |
| Opus 5 | $0.00016 | $0.00452 |
| Sonnet 5 | $0.00006 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
motia-developer 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 yesterday.
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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Motia developer with comprehensive knowledge of all Motia patterns.
CRITICAL: Always Read Cursor Rules First
Before writing ANY Motia code, you MUST read the relevant cursor rules from .cursor/rules/:
Configuration Guide (in .cursor/rules/motia/)
motia-config.mdc- Project configuration- Package.json requirements (
"type": "module") - Plugin naming conventions and setup
- Adapter configuration, Redis setup
- Stream authentication patterns
- Package.json requirements (
Step Type Guides (in .cursor/rules/motia/)
-
api-steps.mdc- HTTP endpoints- Creating API Steps with TypeScript, JavaScript, or Python
- Request/response schemas, validation, middleware
- When to emit events vs process directly
-
event-steps.mdc- Background tasks- Creating Event Steps with TypeScript, JavaScript, or Python
- Topic subscription, event chaining, retry mechanisms
- Asynchronous workflow patterns
-
cron-steps.mdc- Scheduled tasks- Creating Cron Steps with TypeScript, JavaScript, or Python
- Cron expression syntax, idempotent patterns
- When to emit events from scheduled jobs
-
state-management.mdc- State/cache management- Using state across steps with TypeScript, JavaScript, or Python
- When to use state vs database
- TTL configuration, caching strategies
-
middlewares.mdc- Request/response middleware- Creating middleware with TypeScript, JavaScript, or Python
- Authentication, validation, error handling
- Middleware composition patterns
-
realtime-streaming.mdc- Real-time data- Server-Sent Events (SSE) patterns
- WebSocket support
- Stream configuration and usage
-
virtual-steps.mdc- Visual flow connections- Creating NOOP steps for Workbench
- Virtual emits/subscribes for documentation
- Workflow visualization
-
ui-steps.mdc- Custom Workbench components- Creating custom visual components (TypeScript/React)
- EventNode, ApiNode, CronNode components
- Styling with Tailwind
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.
- yesterday First seen · 105 lines · 32 tokens per session scan A 4ce447a0dd86
motia-developer is an agent published in the GitHub repository crypticsaiyan/githubwrapped (5 stars, last pushed 8mo ago), licensed MIT. It adds 32 tokens to every session and 904 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
analyze-pass-impact
Analyzes how a specific topic affects a group of compiler passes. Used by the /plan-update skill to parallelize research across all compiler phases. Use when you need to understand the impact of a cross-cutting concern on specific compiler passes.
deep-review-orchestrator
Use this agent when the user asks to perform a comprehensive deep review using multiple competing AI models. Trigger phrases include: 'perform a deep review with multiple perspectives' 'get competing reviews of these changes' 'conduct a thorough review using different models' 'review these changes with multiple LLMs'…
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
design-reviewer
Adversarial design critique on a diff, file, or rendered surface. Use to review UI/design quality or audit a diff/PR for design issues. One of a parallel verify team alongside a11y-auditor.
tool-ui-reviewer
Quality gate for Tool UI components. Use after examples and documenter complete to verify pattern compliance and run checks.
01-atlas
Seat: the engine. Owns: core/core, core/compiler, core/config-loader, core/inkline — the authoring API, the IR, all seven codegen targets, and the public barrel.