fold: Skill for Claude Code

.claude/skills/perf/SKILL.md

perf is a skill for Claude Code from fold-run/fold. It costs 63 tokens per session (607 once invoked), scanned A, original, Apache-2.0.

A performance guide for a gateway that forwards requests to other services. It defines tests and profiling steps for measuring added delay and memory allocations.

In plain words
What is it for?
Use it when gateway benchmarks fail, when changing request-handling code, or when investigating latency and memory use.
Why use it?
It replaces guesses about speed with repeatable measurements and helps locate the code causing slowdowns.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is fold-run/fold's own configuration. It tells Claude Code how to work on fold 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 fold configures →

Reuse

Borrowing it

Nothing to install: this file belongs to fold-run/fold. 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/fold-run/fold/main/.claude/skills/perf/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/fold-run/fold

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 perf

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/fold-run/fold/perf"><img src="https://agentmods.dev/badge/skills/fold-run/fold/perf.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 607 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.00063 $0.00607
Opus 5.5 $0.00025 $0.00243
Sonnet 5.5 $0.00013 $0.00121
Haiku 4.5 $0.00006 $0.00061

Measured 2mo ago against content hash 22720d0dc8cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

perf 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 2mo 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/skills/perf/SKILL.md · 51 lines

How it starts

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

fold proxy-path performance

The merge gate: added p50 through the gateway < 5 ms (bench/latency_test.go TestAddedLatencyGate, skipped unless FOLD_BENCH=1). Performance here is a test, not a vibe — every claim needs a BENCH_RESULT number behind it.

The gate has a blind spot, by design. Its fixture is one upstream with one trivial tool, so it measures the proxy hop and nothing that scales with federation size. For anything touching the list path — merge, policy filtering, namespacing, cursors — the instrument is go test ./gateway -run '^$' -bench BenchmarkFederatedListTools -benchmem, and allocations per request are the signal to watch (they are stable across machines in a way ns/op is not). FOLD_LOAD_UPSTREAMS / FOLD_LOAD_TOOLS give tools/perf the same federated shape.

Workflow

  1. Measure: launch the bench-profiler agent (yellow) to run the gate, get a clean baseline via stash-bisect if the working diff touched the proxy path, and profile if the gate is blown. It returns numbers and top contributors with file:line.

  2. Fix using the repo's pattern — per-request work moves to snapshot-build time:

    • Anything derivable from config alone (compiled matchers, key prefixes, indexes, namespace tables) is computed once when the routes snapshot is built and read per-request from the snapshot.
    • Hot-path keys: preallocate/intern rather than fmt.Sprintf per request.
    • Never fix latency by buffering less correctly — streaming pass-through is an invisibility requirement, not an optimization.
    • Never fix by loosening the gate threshold or skipping the bench.
  3. Verify: re-run make bench 2–3 times, then make race (snapshot precomputation moves state — races follow), then make check.

  4. Report the before/after BENCH_RESULT lines verbatim.

When the gate fails in CI but passes locally

CI runners are slower and noisier. Compare the CI run's BENCH_RESULT against recent green runs (gh run view --log on both) before concluding regression vs flake. A genuine regression shows in added_p50 relative to direct_p50, not in absolute numbers.

Read the full file on GitHub · 51 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. 2mo ago First seen · 51 lines · 63 tokens per session scan A 22720d0dc8cb

Subscribe to this mod's changes

perf is a skill published in the GitHub repository fold-run/fold (1 stars, last pushed 12d ago), licensed Apache-2.0. It adds 63 tokens to every session and 607 once invoked, about $0.0003 per session on Opus 5.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-31.

Related

perf compared with skills from other repositories

perf next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
perffold-run/foldSkill112d agoApache-2.0A63Claude Code
migrate-goldmark-extension-v1-to-v2yuin/goldmarkSkill5.1k4d agoMITA26Claude Code
use-modern-goJetBrains/go-modern-guidelinesSkill3.9k22d agoApache-2.0A32Claude Code
pi-loop-forensicsdimetron/pi-goSkill2223d agoMITA65Claude Code, Codex
nightly-session-watchdimetron/pi-goSkill2223d agoMITA78Claude Code, Codex
tui-render-debugdimetron/pi-goSkill2223d agoMITA33Claude Code, Codex
memory-minedimetron/pi-goSkill2223d agoMITA35Claude Code