Agent skill · software engineering · jeremylongshore
persona-cost-tuning
Review Persona cost drivers through template policy, duplicate prevention, sandbox use, and measured product quotas. Use when reducing spend without weakening controls. Trigger with: "optimize Persona cost", "Persona usage review", "reduce duplicate inquiries".
Why this skill is useful
Adds specific API integration patterns and caching strategies for optimizing Persona identity verification costs that the AI wouldn't reliably generate on its own.
What it needs
Requires persona account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Persona Verification Policy and Duplicate-Control Review Overview Do not invent price tables or skip required identity evidence. Cost work begins with the business policy and current provider commercial terms, then eliminates accidental duplicate inquiries, unnecessary sessions, polling, and avoidable production testing. Prerequisites Current contract or authorized Dashboard usage data Versioned verification and manual-review policy Inquiry, session, retry, template, and product-quota metrics Instructions Step 1: Establish authority Record billing period, environment, contract source, template versions, verification products, and finance or compliance owner. Treat public examples as non-binding. Step 2: Measure workflow demand Count unique subjects, inquiries, sessions, verification types, retries, abandoned flows, duplicates, manual reviews, and product-quota consumption. Step 3: Find accidental duplication Join internal operation IDs, account references, inquiry IDs, and idempotency evidence. Quantify creates caused by timeouts, races, and client retries. Step 4: Review template policy Compare each verification type with the approved risk tier and regulatory requirement. Changes to evidence requirements need compliance and product approval. Step 5: Shift testing to sandbox Use forced sandbox pass and fail for development and CI because sandbox performs no real checks and has no usage charges. Step 6: Implement and verify Add subject locks, idempotency, event-driven reconciliation, and observability; compare cost and risk indicators before wider rollout. Authentication Cost analysis uses authorized aggregate Dashboard or billing access and minimally scoped Persona API access. Never export customer PII into a finance worksheet. Tool Discipline Use Read and Grep to inspect application configuration, provider documentation, fixtures, schemas, tests, and redacted operational evidence before proposing a change. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/persona-cost-tuning