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 pda-securitygit 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/pda-security)<a href="https://agentmods.dev/skills/plamentsv/plamen/pda-security"><img src="https://agentmods.dev/badge/skills/plamentsv/plamen/pda-security/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/pda-security"><img src="https://agentmods.dev/badge/skills/plamentsv/plamen/pda-security.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.00028 | $0.01245 |
| Opus 5 | $0.00014 | $0.00622 |
| Sonnet 5 | $0.00006 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
pda-security 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 7d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PDA_SECURITY Skill
Trigger Pattern: PDA flag detected (seeds/bump/find_program_address usage) Inject Into: Breadth agents, depth agents Finding prefix:
[PDA-N]Rules referenced: S2, S1
For every PDA in the Solana program:
1. PDA Seed Inventory
List all PDA seed declarations:
| # | PDA Name | Seeds | Purpose | Anchor Constraint | Location |
|---|---|---|---|---|---|
| 1 | {name} | [b"prefix", user.key().as_ref(), &[bump]] |
{what it stores} | seeds = [...], bump |
{file:line} |
2. Canonical Bump Enforcement
For each PDA:
| PDA | Bump Source | Canonical? | Risk if Non-Canonical |
|---|---|---|---|
| {name} | Anchor auto (bump) / find_program_address / USER INPUT |
YES/NO | {if NO: multiple valid addresses} |
Attack (S2): If bump is user-supplied, attacker can use a non-canonical bump to derive a DIFFERENT address that still passes create_program_address. This creates a separate PDA from the intended one.
Defense: Always use find_program_address (returns canonical bump) or Anchor's bump constraint.
3. Seed Collision Analysis
For each PAIR of PDA seed schemas:
| PDA A Seeds | PDA B Seeds | Can Byte Sequences Overlap? | Collision Risk? |
|---|---|---|---|
[b"vault", mint.as_ref()] |
[b"vaultm", ...] |
CHECK: "vault" + mint_bytes could equal "vaultm" + other_bytes? | YES/NO |
Attack: Two different PDA types with seeds that can produce identical byte sequences → one PDA masquerades as another.
Defense: Use unique fixed-length prefixes (e.g., b"vault\x00") or ensure seed structures cannot collide.
4. Seed Uniqueness
For each PDA type, verify seeds include sufficient uniqueness:
| PDA | Unique Per | Seeds Include User/Entity Key? | Could Two Users Share PDA? |
|---|---|---|---|
| {name} | User / Mint / Pool / Global | YES/NO | {if YES: shared state corruption} |
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.
- 7d ago First seen · 111 lines · 28 tokens per session scan A 0554ffba56dc
pda-security is a skill published in the GitHub repository PlamenTSV/plamen (295 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 1,245 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-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.