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-signergit 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-signer)<a href="https://agentmods.dev/skills/berkayoztunc/orquestra/orquestra-signer"><img src="https://agentmods.dev/badge/skills/berkayoztunc/orquestra/orquestra-signer/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-signer"><img src="https://agentmods.dev/badge/skills/berkayoztunc/orquestra/orquestra-signer.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.00092 | $0.00714 |
| Opus 5 | $0.00046 | $0.00357 |
| Sonnet 5 | $0.00018 | $0.00143 |
| Haiku 4.5 | $0.00009 | $0.00071 |
Grade A, and why
orquestra-signer 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 12d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orquestra Signer
Signing and submission skill. Uses ONLY @orquestradev/signer-mcp tools.
This skill is the FINAL step in the pipeline — it never builds or researches.
Constraints
- ONLY use signer-mcp tools:
get_signer_address,sign_transaction,sign_and_send_transaction - NEVER sign without displaying the approval summary first
- NEVER sign without receiving an explicit YES from the user
- NEVER modify the transaction content
- NEVER build or research — this skill receives a ready-made base64 wire tx
- ALWAYS pass
encoding: "base64"in every signing tool call
Setup Requirements
The signer-mcp server requires these environment variables:
SIGNER_KEYPAIR=<base58-encoded-or-JSON-array-keypair>
SOLANA_RPC_URL=<rpc-endpoint>
Signing Protocol (execute every single time)
Step 1 — Identify signing wallet
Call get_signer_address and display:
Signing Wallet: <pubkey>
Step 2 — Show approval summary (MANDATORY)
═══════════════════════════════════════════
TRANSACTION APPROVAL REQUIRED
═══════════════════════════════════════════
Network: <mainnet-beta / devnet>
Signer Wallet: <pubkey>
Program: <program name or ID>
Instruction: <instruction name>
Fee Payer: <pubkey>
Estimated Fee: <lamports> (~$X USD)
Action: <plain English description>
Risk Level: LOW / MEDIUM / HIGH
═══════════════════════════════════════════
Type YES to sign and send, or NO to cancel.
═══════════════════════════════════════════
Step 3 — Wait for explicit approval
- YES → proceed to Step 4
- NO / cancel → stop, do not call any signing tool
- Ambiguous → ask again, do not assume
Step 4 — Sign (and optionally send)
- Sign only: call
sign_transactionwithencoding: "base64"→ return signed base64 wire tx for review - Sign and send: call
sign_and_send_transactionwithencoding: "base64"→ return signature
Both tools must receive
encoding: "base64"in the request payload.
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.
- 12d ago First seen · 80 lines · 0 tokens per session scan A 2492f80e591a
orquestra-signer is a skill published in the GitHub repository berkayoztunc/orquestra (23 stars, last pushed 25d ago), licensed MIT. It adds 92 tokens to every session and 714 once invoked, about $0.0005 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.