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 oyi77/1ai-skills --skill make-scenariosgit clone --depth 1 https://github.com/oyi77/1ai-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/oyi77/1ai-skills/make-scenarios)<a href="https://agentmods.dev/skills/oyi77/1ai-skills/make-scenarios"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/make-scenarios/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/oyi77/1ai-skills/make-scenarios"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/make-scenarios.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.01274 |
| Opus 5 | $0.00017 | $0.00637 |
| Sonnet 5 | $0.00007 | $0.00255 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
make-scenarios 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 11d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Make.com (formerly Integromat) is a visual automation platform with 1500+ app integrations. It uses scenarios with modules connected by routes, with filters, error handlers, and data stores for complex automation logic.
Capabilities
- Build scenarios with 1500+ app modules
- Use routers for conditional branching
- Add filters to control data flow
- Handle errors with error handler routes
- Store data in Data Stores
- Use webhooks for custom triggers
- Schedule scenarios with cron
When to Use
Trigger phrases:
-
"make scenarios"
-
"Automating workflows across SaaS applications"
-
"Needing visual automation with complex branching"
-
"Building customer-facing integrations"
-
Automating workflows across SaaS applications
-
Needing visual automation with complex branching
-
Building customer-facing integrations
-
Managing data synchronization between systems
-
Replacing manual processes with automated scenarios
When NOT to Use
- Task requires custom code (use Pipedream or n8n)
- You need complex data transformations (use ETL tools)
- Task is about data storage, not workflow automation
- You don't have access to the SaaS apps being connected
- Task requires real-time processing (use streaming tools)
- You need to build a custom API (use development tools)
Pseudo Code
Implementation patterns for common use cases with this skill.
Scenario Architecture
Trigger Module → Iterator → Aggregator → Router → Filter → Action
↓
Error Handler → Notify
Module Types
| Type | Examples |
|---|---|
| Trigger | Webhook, Schedule, Email, Form |
| Action | HTTP Request, Send Email, Create Record |
| Search | Get Records, List Items |
| Iterator | Process arrays |
| Aggregator | Combine array items |
| Router | Conditional branching |
| Filter | Stop/continue based on conditions |
Filter Configuration
{
"filter": {
"name": "Only active users",
"conditions": [
{
"field": "{{1.status}}",
"operator": "equal",
"value": "active"
},
{
"field": "{{1.email}}",
"operator": "notEqual",
"value": ""
}
]
}
}
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.
- 11d ago First seen · 228 lines · 34 tokens per session scan A 7dfe16a6a9d5
make-scenarios is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,274 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-30.
Other skills, from other repositories
agent-creator
Create custom AI subagents with proper plugin structure, persona generation, and companion routing skills.
anti-sleep
Keep a Mac awake with caffeinate during long builds, downloads, or supervised automation runs.
workflow-automation
Automate complex workflows and repetitive tasks using AI agents and tool integration. Use when user wants to create automated pipelines, integrate multiple services, or build task-specific agents.
Automation Architect
Design workflow automations using Zapier, Make, n8n, and other automation tools.
hourly-rate-time
A time-management method based on assigning a high personal value to each hour. It treats time as a limited resource and uses that value to decide which tasks to do, outsource, or skip.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.