fast-pinner

Pin API requests to fastest adequate model variants in the Identity harness.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill fast-pinner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fast-pinner
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/fast-pinner
Command: npx skills add https://github.com/AesopScott/mojo --skill fast-pinner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses performance bottlenecks in the Identity harness by allowing operators to pin requests to the fastest adequate model variants, preventing unpredictable latency spikes.

Core Features & Use Cases

  • Performance Control: Explicitly select model variants to trim response times and ensure consistent behavior.
  • Reproducibility: Prevent silent model swaps from altering system outputs by locking in specific providers and versions.
  • Use Case: When a specific API route in the Identity harness experiences high latency, use this skill to identify the bottleneck and pin the request to a faster, optimized model variant.

Quick Start

Use the fast-pinner skill to inspect the current Identity harness performance and apply a pin to the fastest model variant for the identified slow path.

Frequently Asked Questions about fast-pinner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce API latency in the Identity harness?

To reduce API latency in the Identity harness, you can pin requests to the fastest adequate model variants, preventing unpredictable latency spikes and ensuring consistent performance.

How does model pinning prevent silent model swaps?

Model pinning prevents silent model swaps by locking API requests to specific providers and versions, ensuring reproducibility and stopping unpredictable changes to system outputs.

What is the best way to identify performance bottlenecks in model variants?

The best way to identify performance bottlenecks is to inspect current Identity harness performance using observability logs, then pin the identified slow path to a faster optimized model variant.

Do I need configuration files to optimize Identity harness performance?

Yes, you need access to configuration files and observability logs to verify timing improvements and maintain system stability when pinning API requests to faster model variants.

When should I not use model pinning for latency optimization?

You should avoid model pinning when you lack access to configuration files and observability logs, as these are required to verify timing improvements and maintain system stability.