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-migrationgit 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-migration)<a href="https://agentmods.dev/skills/mstr-sharma/strategy-automate/strategy-migration"><img src="https://agentmods.dev/badge/skills/mstr-sharma/strategy-automate/strategy-migration/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-migration"><img src="https://agentmods.dev/badge/skills/mstr-sharma/strategy-automate/strategy-migration.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.00154 | $0.05237 |
| Opus 5.5 | $0.00062 | $0.02095 |
| Sonnet 5.5 | $0.00031 | $0.01047 |
| Haiku 4.5 | $0.00015 | $0.00524 |
Grade A, and why
strategy-migration 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategy migration and promotion
Every import here changes production metadata. Read first, hold a way back before the write (undo package, YAML export or Git commit), read back after. Sign-in and the ops / describe / call mechanics (dry runs, --yes, auto-filled headers): 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 Packages, Migrations, Migration Groups, Project Duplications, Git Service ($API ops --tag strategy-migration) and borrows three Modeling operations for Mosaic models: ms-saveAsDataModel, ms-exportDataModel, ms-restoreDataModel.
Route elsewhere:
- users, groups, security roles, privileges, settings, license, fences →
strategy-admin - reports, dashboards, cubes, folders, object copy/move inside one project, Shared File Store →
strategy-content - subscriptions, schedules →
strategy-distribution - building or editing a Mosaic model, and publish/certify after a copy →
build-mosaic-model(plan withstrategy-data-modeling) - before/after proof of promoted content (Test Center, paired queries) →
strategy-validation - loading the target project, jobs, caches, sessions →
strategy-ops
How to work
- Sign in to each Library you touch. Second environment:
$API --base <Library URL> call …(--basegoes before the subcommand). In bodies an environment is{"id": "<Library URL>", "name": "<label>"}; mstrio sends the URL with a trailing/. $API describe <operationId>before every call. Body skeletons list up to 40 values of an enum.- Reads first: existing records (workflow 9), the objects and their dependents, both projects loaded (
strategy-ops), source and target IDs written down. - Writes: dry run (no
--yes), show it, get a yes, then--yes. Package, migration and duplication writes answer 201/202 and run asynchronously; poll the status read to a terminal state. A 202 is not success.calladdsPrefer: respond-async(the dry run shows it) where the spec requires it (holder PUT/DELETE, imports,triggerValidate,triggerImport*); pass-p Prefer=respond-asyncwhere it is optional but documented (createDuplication*, undo PATCHes). Configuration packages must not carry a project:--project ""overridesMSTR_PROJECT_ID. - Read back status and content, hand the promoted objects to
strategy-validation, then clean up holders, import processes and records you no longer need.
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 · 223 lines · 154 tokens per session scan A c138b17c6ca9
strategy-migration is a skill published in the GitHub repository mstr-sharma/strategy-automate (2 stars, last pushed 2d ago), licensed MIT. It adds 154 tokens to every session and 5,237 once invoked, about $0.0006 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.