Borrowing it
Nothing to install: this file belongs to PIsberg/vibetags. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PIsberg/vibetags/main/.claude/skills/load-tests/SKILL.mdgit clone --depth 1 https://github.com/PIsberg/vibetagsWrote 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/pisberg/vibetags/load-tests)<a href="https://agentmods.dev/skills/pisberg/vibetags/load-tests"><img src="https://agentmods.dev/badge/skills/pisberg/vibetags/load-tests.svg" alt="Measured on agentmods" height="20"></a>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.00094 | $0.02292 |
| Opus 5 | $0.00047 | $0.01146 |
| Sonnet 5 | $0.00019 | $0.00458 |
| Haiku 4.5 | $0.00009 | $0.00229 |
Grade A, and why
load-tests 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 6d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load tests
The harness lives in load-tests/. It is a standalone Maven project that compiles synthetic
annotated sources with and without the processor and subtracts. load-tests/README.md documents
the harness; load-tests/results/README.md documents the baselines. This skill is the judgement
around both: which run answers which question, and which of the resulting numbers may be quoted.
The single most important fact about this harness: most of what it prints is noise on a developer workstation. Two runs of an identical build have differed by up to 1.93x on the JMH hot path. Only the allocation numbers are stable enough to make claims from. Everything below follows from that.
Step 1 — Decide which question is being asked
"Does this change make the processor slower?" Only the allocation sweep can answer that on an ordinary machine, and only if both versions are measured back-to-back in one sitting. See Step 4.
"Capture a baseline for the release." The full capture in Step 3, recorded under
load-tests/results/<version>/ with an env.txt that says what the machine was doing.
"Prove this specific optimisation works." Neither sweep will show it unless it is large.
Write a targeted JMH benchmark or a targeted stress test instead — WriteCacheHitBenchmark and
SignatureCaptureStressTest are the two worked examples in the repo, and both exist because the
general sweeps could not see the effect they were built to measure.
Step 2 — Install the version under test first
The harness resolves vibetags-processor from the local Maven repository. It does not build it.
cd vibetags-annotations && mvn install -DskipTests
cd ../vibetags && mvn install -DskipTests
load-tests/pom.xml sets <processor.version>${revision}</processor.version>, so a plain run
measures whatever version the parent declares. Confirm that rather than assume it:
cd load-tests && mvn dependency:tree | grep vibetags-processor:jar
That line is the only proof that -Dprocessor.version=... reached the dependency. Measuring the
wrong jar produces a result that looks entirely reasonable.
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.
- 6d ago First seen · 160 lines · 94 tokens per session scan A 347d84d41022
load-tests is a skill published in the GitHub repository PIsberg/vibetags (15 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 2,292 once invoked, about $0.0005 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
cgs-soak-test
Use for soak test tasks that plan longer stability checks for memory, performance drift, save/load, networking, and live-ops loops; produce verification evidence, changed or proposed files, and handoff boundaries.
wshobson-backtesting-frameworks
Skill "wshobson-backtesting-frameworks" from ItamarZand88/awesome-agent-conventions, covering backtesting frameworks, when to use this skill, core concepts, 1. backtesting biases and 2. proper backtest structure.
tdd-with-memory
A test-first implementation workflow that recalls past decisions, conventions, and lessons before coding. TDD, or test-driven development, means writing a failing test first, then implementing the code and finally cleaning it up.
ejentum-reasoning-harness
MCP server exposing four cognitive harness modes (reasoning, code, anti-deception, memory). Each call returns an engineered scaffold (failure pattern, procedure, suppression vectors, falsification test) the agent ingests before generating.
lore-onboard
First-time setup wizard for LoreConvo. Verifies the MCP server is connected, the database is accessible, hooks are configured, and runs a test save/load cycle. Use when the user says "set up loreconvo", "onboard", "/lore-onboard", "verify loreconvo", "test loreconvo setup", or after first installing the plugin.
research-wiki
A persistent research knowledge base for storing papers, ideas, experiments, claims, and the links between them.