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 berkayoztunc/orquestra --skill orquestra-pda-explorergit clone --depth 1 https://github.com/berkayoztunc/orquestraWrote 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/berkayoztunc/orquestra/orquestra-pda-explorer)<a href="https://agentmods.dev/skills/berkayoztunc/orquestra/orquestra-pda-explorer"><img src="https://agentmods.dev/badge/skills/berkayoztunc/orquestra/orquestra-pda-explorer/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/berkayoztunc/orquestra/orquestra-pda-explorer"><img src="https://agentmods.dev/badge/skills/berkayoztunc/orquestra/orquestra-pda-explorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 31 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00085 | $0.00640 |
| Opus 5 | $0.00043 | $0.00320 |
| Sonnet 5 | $0.00017 | $0.00128 |
| Haiku 4.5 | $0.00009 | $0.00064 |
Grade A, and why
orquestra-pda-explorer 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 11d 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.
What it actually says
Orquestra PDA Explorer
Account resolution skill. Uses ONLY Orquestra MCP tools to derive PDA addresses, fetch their on-chain data, and iteratively resolve all required accounts.
Constraints
- ONLY use Orquestra MCP tools:
list_pda_accounts,derive_pda,fetch_pda_data,get_program_data - DO NOT search programs, build transactions, or sign anything
- DO NOT guess seed values — ask the user for the exact missing seed
- DO NOT proceed to build if required accounts are still unresolved
Resolution Loop
For each unresolved account:
- Call
list_pda_accounts→ get seed schema for the target account type - Call
derive_pdawith available seeds - Call
fetch_pda_dataon the derived address - Call
get_program_datawhen addresses are not derivable but can be found by program owner, account type, dataSize, memcmp, or fixed-field filters - Extract new pubkeys from returned fields → use to fill other missing accounts
- Repeat until all required accounts are filled
- If a seed is still missing, ask for ONLY that exact seed value
Solana System Constants (use without asking)
| Program | Address |
|---|---|
| System Program | 11111111111111111111111111111111 |
| SPL Token | TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA |
| Token-2022 | TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb |
| ATA Program | ATokenGPvbdGVxr1b2hvZbsiqW5xWH25efTNsLJA8knL |
| Sysvar Rent | SysvarRent111111111111111111111111111111111 |
| Sysvar Clock | SysvarC1ock11111111111111111111111111111111 |
Output Format
For each PDA:
Account Role: <name>
Seeds: [<seed1>, <seed2>]
Derived Address: <base58_address>
On-chain Data: { field: value, ... }
List remaining unresolved accounts with the exact missing seed name. When complete: "All accounts resolved → hand off to orquestra-tx-builder."
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.
- 11d ago First seen · 54 lines · 85 tokens per session scan A 219d8782cf72
orquestra-pda-explorer is a skill published in the GitHub repository berkayoztunc/orquestra (23 stars, last pushed 24d ago), licensed MIT. It adds 85 tokens to every session and 640 once invoked, about $0.0004 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
solana-dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "fuzz my Solana program", "deploy to devnet", "send a v1 transaction", "support larger transactions", "fix maxSupportedTransactionVersion", or "explain…
code-navigation
Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.
alchemy-agentic-gateway
Use when accessing Alchemy APIs for RPC calls, token balances, NFT metadata, asset transfers, transaction simulation, or Alchemy-specific features. Also use when the user mentions "SIWE", "SIWS", "x402", "MPP", "mppx", or "agentic gateway" — this skill covers wallet-based auth flows for Alchemy's x402 and MPP…
alchemy-api
Integrates Alchemy blockchain APIs using an API key. Requires $ALCHEMYAPIKEY to be set; if unavailable, use the alchemy-agentic-gateway skill instead. Use when user asks about EVM JSON-RPC calls, token balances, NFT ownership or metadata, transfer history, token prices, portfolio data, transaction simulation…
slv-validator
Ansible playbooks and Jinja2 templates for deploying and managing Solana validators (mainnet and testnet).
slv-grpc-geyser
Ansible playbooks and Jinja2 templates for deploying and managing Solana gRPC Geyser streaming nodes.