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-tx-buildergit 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-tx-builder)<a href="https://agentmods.dev/skills/berkayoztunc/orquestra/orquestra-tx-builder"><img src="https://agentmods.dev/badge/skills/berkayoztunc/orquestra/orquestra-tx-builder/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-tx-builder"><img src="https://agentmods.dev/badge/skills/berkayoztunc/orquestra/orquestra-tx-builder.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.00072 | $0.00642 |
| Opus 5 | $0.00036 | $0.00321 |
| Sonnet 5 | $0.00014 | $0.00128 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
orquestra-tx-builder 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orquestra TX Builder
Transaction construction skill. Uses ONLY Orquestra MCP's build_instruction tool
to produce a base64-encoded wire transaction (Solana RPC standard, encoding: "base64").
Constraints
- ONLY use Orquestra MCP tool:
build_instruction - DO NOT call
build_instructionwith placeholder or guessed values - DO NOT search programs or derive PDAs — use upstream research results
- DO NOT sign or send — hand off to
orquestra-signer
Pre-Build Checklist
All items must be confirmed before calling build_instruction:
-
program_id— exact base58 program address -
instruction_name— exact instruction name from Orquestra - All required accounts — base58 addresses with signer/writable flags
- All required arguments — values with correct types (u64, Pubkey, etc.)
-
fee_payer— wallet pubkey that pays the transaction fee
If ANY item is missing:
- Missing account → ask user to run
orquestra-pda-explorerfirst, or ask for exact address - Missing argument → ask for the argument name and its expected type
- NEVER proceed with unknowns
Output Format
Pre-Build Summary
Program: <name> (<program_id>)
Instruction: <instruction_name>
Fee Payer: <pubkey>
Accounts:
[0] authority <pubkey> signer=true writable=false
[1] vault <pubkey> signer=false writable=true
Arguments:
amount: 1500000000 (u64, lamports)
Unsigned Transaction (base64 wire format)
Encoding: base64
Wire TX: <base64_encoded_wire_tx>
Solana wire-format transaction serialized as base64. Submit to RPC with
encoding: "base64"in the request body.
RPC submission header (for manual use)
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "sendTransaction",
"params": [
"<base64_encoded_wire_tx>",
{ "encoding": "base64", "preflightCommitment": "confirmed" }
]
}
Next Step
"Pass this base64 wire transaction to orquestra-signer to sign and send."
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 · 77 lines · 72 tokens per session scan A e67118a3dc70
orquestra-tx-builder is a skill published in the GitHub repository berkayoztunc/orquestra (23 stars, last pushed 25d ago), licensed MIT. It adds 72 tokens to every session and 642 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.