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-unified-analyticsgit 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-unified-analytics)<a href="https://agentmods.dev/skills/iapro-community/orquestrador-maestro/skill-unified-analytics"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-unified-analytics/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-unified-analytics"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-unified-analytics.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.00046 | $0.00829 |
| Opus 5 | $0.00023 | $0.00415 |
| Sonnet 5 | $0.00009 | $0.00166 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
skill-unified-analytics 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 9d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Unified Analytics
Use this skill when adding or improving telemetry, metrics, funnels, product dashboards, admin reporting, billing analytics, or usage observability. Treat analytics as a product contract, not incidental logging.
Workflow
- Define the decision the metric supports before adding events or charts.
- Inventory existing providers, server logs, database tables, queues, webhooks, feature flags, and analytics helpers.
- Choose the source of truth: client event, server event, durable audit log, billing provider, warehouse table, or pre-aggregated view.
- Define the event or metric contract before implementation: name, trigger, owner, required properties, optional properties, identity fields, privacy level, and version.
- Instrument once at the boundary that best represents truth. Avoid duplicate client and server events unless reconciliation is intentional.
- Validate with a local log, test, provider debugger, database row, or dashboard query before completion.
Event Taxonomy
- Use names in a stable pattern such as
object_actionor the project's existing convention. - Prefer business events over UI implementation details:
checkout_started,subscription_upgraded,report_exported. - Include context that enables segmentation: tenant/account, user role, plan, feature, source, campaign, environment, and request/job identifiers where allowed.
- Do not send raw secrets, tokens, passwords, full payment data, private content, or unnecessary PII.
- Version payloads when shape or semantics change:
schema_version, migration notes, or compatibility handling. - Keep idempotency keys or event IDs for server events that may retry.
SaaS Metric Map
- Activation: signup completed, onboarding completed, first useful action, invitation accepted, workspace created.
- Engagement: active account, retained user, feature used, report viewed, export completed, workflow completed.
- Revenue: trial started, checkout started, payment succeeded, subscription changed, invoice failed, refund, churn.
- Usage and cost: quota consumed, job processed, AI tokens/spend, storage used, seats used, API calls.
- Reliability: job failed, webhook failed, sync delayed, queue latency, API error, retry exhausted.
- Admin and security: permission changed, manual override, impersonation started, user blocked, audit export, policy violation.
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.
- 9d ago First seen · 66 lines · 46 tokens per session scan A de9d493b18c8
skill-unified-analytics is a skill published in the GitHub repository IAPro-Community/Orquestrador-Maestro (42 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 829 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-09-03.
Other skills, from other repositories
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
dry-run
Preview command effects without making changes. Simulates file writes, git operations, agent spawns, and state changes. All reads execute normally for accurate preview. Use --dry-run flag on any command.
task-breakdown-phase
Standard Operating Procedure for /tasks phase. Covers task sizing, acceptance criteria definition, and TDD-first task sequencing. (project).
finalize-phase
Completes feature/epic workflows after deployment with comprehensive walkthrough generation for epics (v5.0+), roadmap updates, artifact archival, documentation, and branch cleanup. Use after /ship-prod, /deploy-prod, or /build-local completes, or when user asks to finalize. (project).
dependency-conflict-resolver
Detect and resolve package dependency conflicts before installation across npm/yarn/pnpm, pip/poetry, cargo, and composer. Auto-trigger when installing/upgrading packages. Validates peer dependencies, version compatibility, security vulnerabilities. Auto-resolves safe conflicts (patches, dev deps), suggests manual…
staging-deployment-phase
Deploys features to staging environment with database migrations, health checks, and deployment verification. Use during /ship-staging phase or when deploying to staging environments for validation before production release.