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/zero-state-returnnpx skills add PlamenTSV/plamen --skill zero-state-returngit 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/zero-state-return)<a href="https://agentmods.dev/skills/plamentsv/plamen/zero-state-return"><img src="https://agentmods.dev/badge/skills/plamentsv/plamen/zero-state-return.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.00021 | $0.02838 |
| Opus 5 | $0.00010 | $0.01419 |
| Sonnet 5 | $0.00004 | $0.00568 |
| Haiku 4.5 | $0.00002 | $0.00284 |
Grade A, and why
zero-state-return 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ZERO_STATE_RETURN Skill
Trigger Pattern: Vault/pool/first-depositor pattern detected Inject Into: Depth-edge-case Purpose: Analyze zero-state transitions in Aptos Move protocols -- initial zero state, return to zero after operations, residual assets, and re-entry vulnerabilities
Overview
This skill covers BOTH initial zero state AND return-to-zero-state analysis:
- Protocol initialization and first deposit conditions
- Protocol returning to zero after normal operations
- Residual assets when supply returns to zero
- Re-entry vulnerabilities after full exit
1. Identify Zero-State Transitions
Find all vault/pool/staking mechanisms and their zero-state boundaries:
| State | Resource / Variable | Zero Condition | Trigger | Code Location |
|---|---|---|---|---|
| Total shares | {resource.total_supply} | == 0 |
All users withdrew/burned | {module:line} |
| Total assets | {resource.total_assets} | == 0 |
No funds deposited | {module:line} |
| Pool liquidity | {resource.reserves} | Both reserves == 0 |
All LP withdrawn | {module:line} |
| Staking pool | {resource.total_staked} | == 0 |
All unstaked | {module:line} |
For each state: what is the protocol behavior when this condition is true?
2. First Depositor Analysis
Can the first depositor manipulate share price?
2a. Share Minting Formula at Zero State
| Protocol | Formula | When totalShares == 0 | First Deposit Behavior |
|---|---|---|---|
| {name} | shares = amount * totalShares / totalAssets |
{special case?} | {describe} |
Classic first depositor attack on Aptos:
- First depositor deposits minimal amount (e.g., 1 unit)
- Attacker directly deposits tokens to the protocol's FungibleStore (unsolicited -- bypasses accounting)
- Exchange rate inflates:
totalAssetsincreases buttotalSharesstays at 1 - Next depositor receives 0 shares due to rounding (their deposit amount < inflated share price)
- First depositor withdraws, capturing the second depositor's funds
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 · 244 lines · 21 tokens per session scan A cdd1f2e03835
zero-state-return is a skill published in the GitHub repository PlamenTSV/plamen (281 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 2,838 once invoked, about $0.0001 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.