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 mstr-sharma/strategy-automate --skill strategy-opsgit clone --depth 1 https://github.com/mstr-sharma/strategy-automateWrote 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/mstr-sharma/strategy-automate/strategy-ops)<a href="https://agentmods.dev/skills/mstr-sharma/strategy-automate/strategy-ops"><img src="https://agentmods.dev/badge/skills/mstr-sharma/strategy-automate/strategy-ops/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/mstr-sharma/strategy-automate/strategy-ops"><img src="https://agentmods.dev/badge/skills/mstr-sharma/strategy-automate/strategy-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00199 | $0.04539 |
| Opus 5.5 | $0.00080 | $0.01816 |
| Sonnet 5.5 | $0.00040 | $0.00908 |
| Haiku 4.5 | $0.00020 | $0.00454 |
Grade A, and why
strategy-ops 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 12d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategy operations and monitoring
Reads here are cheap; most writes hit everyone on a node. Act on the requesting user's own jobs and sessions unless told otherwise, and ask before purging, unloading or disconnecting on a shared environment. Sign-in and the ops / describe / call mechanics (dry runs, --yes): skills/strategy-platform/SKILL.md. Commands run from the repo root with API="python3 skills/strategy-platform/scripts/strategy_api.py".
Scope
Owns the spec tags Monitors, Telemetry, Change Journal, Scripts, Tasks, Flows, plus the internal-only Performance Statistics, HangDetector, Workflows, Insight Engine ($API ops --tag strategy-ops [--internal]).
Route elsewhere:
- users, groups, security roles, privileges, settings, license audit and compliance, fences →
strategy-admin - report, dashboard and cube definitions, cube refresh, object search →
strategy-content; Mosaic publish →build-mosaic-model(memory/reference_mosaic_publish_path.md) - subscriptions and schedules (a task runs on a schedule object) →
strategy-distribution - packages, migrations, project duplication →
strategy-migration - Test Center comparisons and numeric validation →
strategy-validation
How to work
- Sign in, then check what you may see:
$API call getClusterNodes. With Use Cluster Monitor it returns full node detail; with only a user-connection, cache, cube or job monitor privilege, node names; with none, 403. - Job, cache and DB-connection monitors work per node: take
nodes[].namefromgetClusterNodesand loop. - Who am I:
$API call sessionSessionIdUserInfoGetgivesidandfullName. The job monitor filters on full name (user); the connection monitor on login (username) or full name (name). $API describe <operationId>before each call; reads first; writes as a dry run, then--yesafter the user agrees; read back (the job is gone, the cache state changed, the project reachedloaded).- Many writes answer 202 (cube cache changes, project status, change journal purge): poll until done.
- Every
$API callis its own sign-in unless you pass--reuse-session(MSTR_REUSE_SESSION=1) or use a cachedssosession, and project operations open a project session (memory/feedback_build_mosaic_session_leak.md). Use a reused session for polling loops and end it withstrategy_auth.py logout.
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.
- 12d ago First seen · 162 lines · 199 tokens per session scan A 9451e0a4dc7c
strategy-ops is a skill published in the GitHub repository mstr-sharma/strategy-automate (2 stars, last pushed 2d ago), licensed MIT. It adds 199 tokens to every session and 4,539 once invoked, about $0.0008 per session on Opus 5.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-10-06.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".