Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add fabric-testbed/claude-plugin-marketplace --skill fabric-benchmarkinggit clone --depth 1 https://github.com/fabric-testbed/claude-plugin-marketplaceWrote 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/fabric-testbed/claude-plugin-marketplace/fabric-benchmarking)<a href="https://agentmods.dev/skills/fabric-testbed/claude-plugin-marketplace/fabric-benchmarking"><img src="https://agentmods.dev/badge/skills/fabric-testbed/claude-plugin-marketplace/fabric-benchmarking/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.
<a href="https://agentmods.dev/skills/fabric-testbed/claude-plugin-marketplace/fabric-benchmarking"><img src="https://agentmods.dev/badge/skills/fabric-testbed/claude-plugin-marketplace/fabric-benchmarking.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.01931 |
| Opus 5 | $0.00010 | $0.00966 |
| Sonnet 5 | $0.00004 | $0.00386 |
| Haiku 4.5 | $0.00002 | $0.00193 |
Grade B, and why
fabric-benchmarking scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
node1.add_post_boot_execute('sudo node_tools/host_tune.sh') How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
When invoked, generate code for network performance benchmarking on FABRIC using iPerf3. Three tiers:
- Basic — iPerf3 over FABNet with Docker containers
- Optimized — CPU pinning, NUMA tuning, and host_tune.sh
- SmartNIC — Dedicated ConnectX NICs with full hardware optimization
Help the user choose the right level and generate complete code.
API Reference
Performance Tuning
node.pin_cpu(component_name='nic1') # Pin vCPUs to NIC's NUMA node
node.numa_tune() # Pin memory to same NUMA node
node.os_reboot() # Reboot to apply
Post-Reboot Reconfiguration
slice.wait_ssh()
for node in slice.get_nodes():
node.config() # Re-configure network interfaces
Patterns
Basic iPerf3 (FABNet + Docker)
from fabrictestbed_extensions.fablib.fablib import FablibManager
fablib = FablibManager()
[site1, site2] = fablib.get_random_sites(count=2)
slice = fablib.new_slice(name="iperf3-basic")
node1 = slice.add_node(
name="server",
site=site1,
cores=4,
ram=16,
disk=50,
image="default_rocky_9",
)
node1.add_fabnet()
node1.add_post_boot_upload_directory('node_tools', '.')
node1.add_post_boot_execute('sudo node_tools/host_tune.sh')
node1.add_post_boot_execute('node_tools/enable_docker.sh {{ _self_.image }}')
node1.add_post_boot_execute(
'docker pull fabrictestbed/slice-vm-rocky8-multitool:0.0.2'
)
node2 = slice.add_node(
name="client",
site=site2,
cores=4,
ram=16,
disk=50,
image="default_rocky_9",
)
node2.add_fabnet()
node2.add_post_boot_upload_directory('node_tools', '.')
node2.add_post_boot_execute('sudo node_tools/host_tune.sh')
node2.add_post_boot_execute('node_tools/enable_docker.sh {{ _self_.image }}')
node2.add_post_boot_execute(
'docker pull fabrictestbed/slice-vm-rocky8-multitool:0.0.2'
)
slice.submit()
server = slice.get_node(name="server")
client = slice.get_node(name="client")
server_addr = server.get_interface(
network_name=f"FABNET_IPv4_{server.get_site()}"
).get_ip_addr()
# Start iPerf3 server (single test mode)
server.execute(
"docker run -d --rm --network host "
"fabrictestbed/slice-vm-rocky8-multitool:0.0.2 iperf3 -s -1"
)
# Run iPerf3 client (4 parallel streams, 30 sec, 10 sec omit)
stdout, stderr = client.execute(
f"docker run --rm --network host "
f"fabrictestbed/slice-vm-rocky8-multitool:0.0.2 "
f"iperf3 -c {server_addr} -P 4 -t 30 -i 10 -O 10"
)
print(stdout)
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.
- 11d ago First seen · 252 lines · 21 tokens per session scan B 2ced395b8413
fabric-benchmarking is a skill published in the GitHub repository fabric-testbed/claude-plugin-marketplace (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,931 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…