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 IAPro-Community/Orquestrador-Maestro --skill skill-saas-core-limitsgit clone --depth 1 https://github.com/IAPro-Community/Orquestrador-MaestroWrote 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/iapro-community/orquestrador-maestro/skill-saas-core-limits)<a href="https://agentmods.dev/skills/iapro-community/orquestrador-maestro/skill-saas-core-limits"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-saas-core-limits/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/iapro-community/orquestrador-maestro/skill-saas-core-limits"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-saas-core-limits.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.00051 | $0.00598 |
| Opus 5 | $0.00026 | $0.00299 |
| Sonnet 5 | $0.00010 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
skill-saas-core-limits 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skill-saas-core-limits
Workflow
- Identify the billable actor: user, tenant, workspace, account, organization, or project.
- Inventory gated features and usage counters. Classify each as hard limit, soft limit, feature flag, trial-only feature, admin override, or informational banner.
- Model entitlements independently from payment provider objects. Store provider IDs as evidence, not as the product access model.
- Enforce important limits server-side, in RPC, or through RLS. Use frontend checks only for early feedback.
- Make usage updates atomic when races are possible.
- Add audit logs for payment sync, admin overrides, blocked states, automatic deactivation, and limit resets.
- Verify transitions with focused tests, SQL checks, or manual scenarios.
Data Model
plans: code, display name, active flag, currency, price, interval, feature limits JSON.entitlements: actor ID, plan ID, status, starts_at, ends_at, grace_until, provider, provider IDs, override fields.usage_counters: actor ID, feature key, period start/end, used count, hard limit, reset policy.audit_logs: actor, action, before/after, reason, source, correlation ID.
Status Contract
- Subscription/access states:
trialing,active,grace,past_due,cancelled,expired,blocked. - Usage states:
ok,caution,warning,limit_reached,expired. - Suggested thresholds:
cautionat 70%,warningat 90%,limit_reachedat 100%.
Guardrails
- Do not grant or revoke access from a checkout success redirect alone.
- Do not trust frontend counters for enforcement.
- Do not scatter plan logic across UI components. Centralize in backend services, RPC, or shared domain helpers.
- Do not block paid users silently. Return actionable errors and show upgrade/recovery paths.
- Keep grace-period and cancellation policy explicit; do not infer it from provider defaults.
Local Reference
For a concrete local pattern, inspect {{USER_HOME}}/Documents\Code\Nina\src\lib\planLimitChecker.ts only when implementing similar Supabase/RPC usage checks.
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 · 53 lines · 51 tokens per session scan A 45125d21c293
skill-saas-core-limits is a skill published in the GitHub repository IAPro-Community/Orquestrador-Maestro (42 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 598 once invoked, about $0.0003 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-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
composio
Build AI agents and apps with Composio - access 200+ external tools with Tool Router or direct execution.
fortify
Use when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.
annie-universal-api-orchestrator
Use AGNT's stored OAuth tokens and API keys for a third-party API only when no suitable authenticated AGNT tool exists or a working tool lacks the required API capability. Existing provider tools are always the first choice.
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
lwip-integration
Use when integrating, porting, configuring, or debugging lwIP TCP/IP stack, netif drivers, memory pools, sysarch, DHCP, TCP, UDP, or embedded networking issues.