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 agentmods add skills/plamentsv/plamen/migration-analysisnpx skills add PlamenTSV/plamen --skill migration-analysisgit clone --depth 1 https://github.com/PlamenTSV/plamenWrote 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/plamentsv/plamen/migration-analysis)<a href="https://agentmods.dev/skills/plamentsv/plamen/migration-analysis"><img src="https://agentmods.dev/badge/skills/plamentsv/plamen/migration-analysis.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.03517 |
| Opus 5 | $0.00022 | $0.01758 |
| Sonnet 5 | $0.00009 | $0.00703 |
| Haiku 4.5 | $0.00004 | $0.00352 |
Grade A, and why
migration-analysis 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 4d 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: MIGRATION_ANALYSIS
Trigger: Protocol has migration patterns (reinitialize, V2/V3, deprecated, upgrade, legacy, Coin-to-FA) Covers: Token type mismatches, stranded assets, interface incompatibilities, module upgrade safety Required: YES when MIGRATION flag detected
Aptos Migration Context
Aptos modules are upgradeable by default under the compatible upgrade policy. Key differences from EVM:
- Module upgrades are in-place (same address, same module name)
- Resources in global storage persist across upgrades unchanged
- New functions can be added; existing public function signatures must remain compatible
- Storage layout must be compatible: new fields only at end of structs, existing fields unchanged
immutablepolicy freezes module permanently;compatibleallows additive changes- The
Coin<T>toFungibleAssetmigration is a major ecosystem-wide transition
Trigger Patterns
V2|V3|_deprecated|migrat|upgrade|legacy|old_token|new_token|coin_to_fungible|fungible_asset_to_coin|reinitialize
Reasoning Template
Step 1: Identify Token Transitions
Find all token migration patterns:
Coin<T>toFungibleAssetmigration (ecosystem-wide)- Legacy module interfaces still referenced
- Deprecated functions still callable
- V1 -> V2 module patterns within the protocol
For each transition:
| Old Standard/Type | New Standard/Type | Migration Function | Bidirectional? | Framework Support? |
|---|---|---|---|---|
| Coin | FungibleAsset | coin::coin_to_fungible_asset | YES (coin::fungible_asset_to_coin) | aptos_framework |
| ModuleV1::Resource | ModuleV2::Resource | custom migrate() | {YES/NO} | N/A |
Step 2: Check Interface Compatibility
For each external call that involves migrated tokens or upgraded modules:
- What type does the CALLER expect? (
Coin<T>orFungibleAssetorObject<Metadata>) - What type does the CALLEE actually return/accept?
- Are they the same?
- Has the external module upgraded to use a different standard?
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.
- 4d ago First seen · 311 lines · 43 tokens per session scan A c9b5fe47d409
migration-analysis is a skill published in the GitHub repository PlamenTSV/plamen (281 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 3,517 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
prowler-ui
Prowler UI-specific patterns. For generic patterns, see: typescript, react-19, nextjs-16, tailwind-4. Trigger: When working inside ui/ on Prowler-specific conventions (shadcn, folder placement, actions/adapters, shared types/hooks/lib).
prowler-pr
Creates Pull Requests for Prowler following the project template and conventions. Trigger: When working on pull request requirements or creation (PR template sections, PR title Conventional Commits check, changelog gate/no-changelog label), or when inspecting PR-related GitHub workflows like conventional-commit.yml…
tailwind-4
Tailwind CSS 4 patterns and best practices. Trigger: When styling with Tailwind (className, variants, cn()), especially when dynamic styling or CSS variables are involved (no var() in className).
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
prowler
Main entry point for Prowler development - quick reference for all components. Trigger: General Prowler development questions, project overview, component navigation (NOT PR CI gates or GitHub Actions workflows).
prowler-tour
Keeps product-tour definitions aligned with the UI features they describe. Trigger: When modifying UI components that have associated tours, editing tour definition files, or renaming data-tour-id attributes.