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 PlamenTSV/plamen --skill validator-lifecycle-and-slashinggit 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/validator-lifecycle-and-slashing)<a href="https://agentmods.dev/skills/plamentsv/plamen/validator-lifecycle-and-slashing"><img src="https://agentmods.dev/badge/skills/plamentsv/plamen/validator-lifecycle-and-slashing/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/plamentsv/plamen/validator-lifecycle-and-slashing"><img src="https://agentmods.dev/badge/skills/plamentsv/plamen/validator-lifecycle-and-slashing.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.00045 | $0.02742 |
| Opus 5 | $0.00023 | $0.01371 |
| Sonnet 5 | $0.00009 | $0.00548 |
| Haiku 4.5 | $0.00005 | $0.00274 |
Grade A, and why
validator-lifecycle-and-slashing 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 6d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Injectable Skill: Validator Lifecycle and Slashing
L1 trigger:
L1_PATTERN=trueAND (slashing/ORvalidator/ORstaking/ORx/slashingORx/stakingORunbondingORdelegatordetected in recon subsystem map) Inject Into:depth-state-traceordepth-consensus-invariantLanguage: Go and Rust Finding prefix:[VL-N]Status: v0.1 draft (added from Round 4 gap analysis)
Orchestrator Decomposition Guide
- Section 1: depth-state-trace (lifecycle state machine)
- Section 2: depth-consensus-invariant (slashing correctness)
- Section 3: depth-edge-case (boundary conditions on stake math)
When This Skill Activates
Recon identifies a PoS / DPoS / BFT staking subsystem. This skill is ADJACENT to but distinct from fork-choice-audit and consensus-safety-invariants: those cover "which chain is head" and "does the state machine stay consistent," while this one covers "who counts as a validator right now, and when must they be punished."
Round 4 gap analysis identified this as a pattern with ≥3 public exemplars not well-covered by the existing skill pack.
1. Lifecycle State Machine
Every staking system has a finite state machine for validator status. Common states:
| State | Meaning | Typical transitions |
|---|---|---|
| Pending / Deposited | Funds deposited, not yet active | → Active (on epoch boundary) |
| Active | Currently producing blocks / signing attestations | → Exiting (voluntary), → Slashed (on misbehavior), → Jailed (on downtime) |
| Exiting | Requested to leave, funds locked | → Unbonding |
| Unbonding | Exit period elapsing; still slashable | → Withdrawable |
| Withdrawable | Funds claimable | → (removed) |
| Jailed / Tombstoned | Temporarily removed for downtime | → Active (on unjail) |
| Slashed | Permanently penalized | → Unbonding (with reduced stake) |
Check per transition
- Enumerate every state transition in the validator state machine
- For each, identify the trigger (epoch boundary, tx message, slashing evidence, timeout)
- For each transition, enumerate the state variables that MUST be updated (active set, delegator shares, power index, reward accumulator, slashing index)
- Check: does every code path through the transition update ALL variables?
- Check idempotency: can the same transition fire twice? What happens?
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.
- 6d ago First seen · 174 lines · 45 tokens per session scan A e1a0e8088caf
validator-lifecycle-and-slashing is a skill published in the GitHub repository PlamenTSV/plamen (295 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 2,742 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
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
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.
evm-bytecode-analysis
Analyze supplied deployed EVM runtime bytecode with EVMole or guide a separate application in integrating a published EVMole Rust, Go, Python, or JavaScript binding. Use for unverified-contract inspection, ABI reconstruction from runtime code, selector discovery, storage-access analysis, EVM control-flow inspection…
talos-action-development
Develop, modify, review, and maintain standalone Talos actions in contracts/tasks/actions, including chain guardrails, contract bindings, transaction safety, schedules, action catalogues, and Talos documentation. Use when adding an action, changing an action’s behavior or parameters, updating a Talos schedule, or…
web3-poc-foundry
Complete Foundry PoC writing guide + all cheatcodes + DeFiHackLabs reproduction patterns. Use this when building a proof of concept exploit, setting up a fork test, using Foundry cheatcodes, or reproducing a known DeFi hack for learning.
web3-grep-arsenal
Master grep command arsenal for Web3 smart contract auditing. Use when starting a new protocol scan, before deep code review, or when hunting specific vulnerability classes.