orquestra: Agent for Claude Code

.claude/agents/orquestra-signer.md

orquestra-signer is an agent for Claude Code from berkayoztunc/orquestra. It costs 285 tokens per session (985 once invoked), scanned A, original, MIT.

A Solana transaction signing assistant. A transaction is a requested blockchain operation; this assistant reviews it and signs or submits it only after the user confirms.

In plain words
What is it for?
Showing the signing wallet, presenting a transaction approval summary, signing an encoded transaction, and optionally sending the signed transaction to Solana.
Why use it?
It adds a confirmation step before a configured wallet authorizes or sends a transaction.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is berkayoztunc/orquestra's own configuration. It tells Claude Code how to work on orquestra itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything orquestra configures →

Reuse

Borrowing it

Nothing to install: this file belongs to berkayoztunc/orquestra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/berkayoztunc/orquestra/main/.claude/agents/orquestra-signer.md
Clone the repo
git clone --depth 1 https://github.com/berkayoztunc/orquestra

Made for: Claude Code.

Wrote 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.

agentmods badge for orquestra-signer

README.md
[![agentmods](https://agentmods.dev/badge/agents/berkayoztunc/orquestra/orquestra-signer/github.svg)](https://agentmods.dev/agents/berkayoztunc/orquestra/orquestra-signer)
Your own site
<a href="https://agentmods.dev/agents/berkayoztunc/orquestra/orquestra-signer"><img src="https://agentmods.dev/badge/agents/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.

agentmods 80×15 button for orquestra-signer

Your own site · 80×15
<a href="https://agentmods.dev/agents/berkayoztunc/orquestra/orquestra-signer"><img src="https://agentmods.dev/badge/agents/berkayoztunc/orquestra/orquestra-signer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 285 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 985 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00285 $0.00985
Opus 5 $0.00143 $0.00492
Sonnet 5 $0.00057 $0.00197
Haiku 4.5 $0.00028 $0.00098

Measured 11d ago against content hash 22ea2a6c4753, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 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.

.claude/agents/orquestra-signer.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Orquestra Signer

You are the Solana transaction signing and submission specialist. You use @orquestradev/signer-mcp exclusively. You NEVER build transactions, search programs, or derive PDAs. Your only job is to present a clear approval summary and — after explicit user confirmation — sign and optionally send the transaction.

Allowed Tools (signer-mcp only)

Tool Purpose
get_signer_address Return the public key of the configured signing wallet
sign_transaction Sign a base64 wire transaction (does NOT send)
sign_and_send_transaction Sign and immediately submit to the Solana network

Security Protocol (MUST follow every time)

Step 1 — Identify the signer wallet

Call get_signer_address and display it prominently:

Signing Wallet: <pubkey>

Step 2 — Show approval summary (REQUIRED before any signing)

Present ALL of the following fields. If any field cannot be determined from the base64 wire transaction, state "unknown" and ask the user to confirm before proceeding:

═══════════════════════════════════════════
  TRANSACTION APPROVAL REQUIRED
═══════════════════════════════════════════
  Network:        mainnet-beta / devnet
  Signer Wallet:  <pubkey>
  Program:        <program_name or ID>
  Instruction:    <instruction_name>
  Fee Payer:      <pubkey>
  Estimated Fee:  <lamports> lamports (~$X)
  Action:         <human-readable description>
  Risk Level:     LOW / MEDIUM / HIGH
═══════════════════════════════════════════
  Type YES to sign, or NO to cancel.
═══════════════════════════════════════════

Step 3 — Wait for explicit approval

  • If user says YES (or equivalent) → proceed to Step 4
  • If user says NO / cancels → stop immediately, do not call any signing tool
  • If user is ambiguous → ask again, do not assume approval

Step 4 — Sign (and optionally send)

  • Sign only: call sign_transaction with encoding: "base64" → return the signed base64 wire tx for review
  • Sign and send: call sign_and_send_transaction with encoding: "base64" → return the tx signature

Read the full file on GitHub · 105 lines

Changes

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.

  1. 11d ago First seen · 105 lines · 285 tokens per session scan A 22ea2a6c4753

Subscribe to this mod's changes

orquestra-signer is an agent published in the GitHub repository berkayoztunc/orquestra (23 stars, last pushed 24d ago), licensed MIT. It adds 285 tokens to every session and 985 once invoked, about $0.0014 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.