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-slice-creategit 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-slice-create)<a href="https://agentmods.dev/skills/fabric-testbed/claude-plugin-marketplace/fabric-slice-create"><img src="https://agentmods.dev/badge/skills/fabric-testbed/claude-plugin-marketplace/fabric-slice-create/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-slice-create"><img src="https://agentmods.dev/badge/skills/fabric-testbed/claude-plugin-marketplace/fabric-slice-create.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.00017 | $0.02238 |
| Opus 5 | $0.00009 | $0.01119 |
| Sonnet 5 | $0.00003 | $0.00448 |
| Haiku 4.5 | $0.00002 | $0.00224 |
Grade A, and why
fabric-slice-create 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 12d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
When invoked, generate code to create a FABRIC experiment slice. Ask the user about:
- Slice name
- Number and type of nodes (cores, RAM, disk, image, site)
- Any special components (GPUs, NICs, NVMe, FPGAs)
- Network connectivity needs (L2, L3/FABnet, none)
- Post-boot configuration needs
Generate complete, working code including error handling and cleanup on failure.
Use the modern API patterns:
- For networks: create the network first, then use
iface.set_mode('auto')andnet.add_interface(iface) - For L3 routing: use
node.add_route(subnet=fablib.FABNETV4_SUBNET, next_hop=net.get_gateway()) - For node FABnet shortcut: use
node.add_fabnet()for simple cases
API Reference
Creating a Slice
slice = fablib.new_slice(name="my-slice") -> Slice
Adding Nodes
node = slice.add_node(
name: str, # Required: unique node name
site: str = None, # Site name (random if None)
cores: int = 2, # Number of CPU cores
ram: int = 8, # RAM in GB
disk: int = 10, # Disk in GB
image: str = None, # OS image (default: latest Ubuntu)
instance_type: str = None, # Alternative to cores/ram/disk
host: str = None, # Specific host at site
user_data: dict = {}, # Custom metadata
validate: bool = False, # Inline validation
raise_exception: bool = True, # Raise on validation failure
) -> Node
Adding Components to Nodes
component = node.add_component(
model: str = None, # Component model string (see resource-discovery skill)
name: str = None, # Unique component name
) -> Component
# Get interfaces from a component
ifaces = component.get_interfaces()
iface = ifaces[0]
Interface Configuration
# Set auto mode for automatic IP configuration
iface.set_mode('auto') # 'auto', 'manual', or 'config'
# Add interface to a network
net.add_interface(iface)
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.
- 12d ago First seen · 318 lines · 17 tokens per session scan A e6ce9ad8f3ec
fabric-slice-create 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 17 tokens to every session and 2,238 once invoked, about $0.0001 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-31.
Other skills, from other repositories
neuroskill-bci
Use live BCI cognitive and mood state from NeuroSkill.
ruview-advanced-sensing
Advanced RuView capabilities — RuvSense multistatic sensing (attention-weighted fusion, geometric diversity, persistent field model), cross-viewpoint fusion across multiple nodes, RF tomography (ISTA L1 solver, voxel grids), longitudinal biomechanics drift, pre-movement intention signals, adversarial signal detection…
ruview-applications
Run RuView sensing applications — presence/occupancy, breathing & heart rate, activity & fall detection, 17-keypoint pose estimation (WiFlow), sleep monitoring & apnea screening, environment mapping, Mass Casualty Assessment (MAT), and the 3D point-cloud fusion demo. Use when someone wants to actually do something…
lab-hardware-cad
Design custom laboratory hardware as parametric build123d models and export fabrication-ready STEP, STL, and DXF files - microfluidic chips and molds, optomechanical mounts and breadboard adapters, cuvette and microplate holders, tube racks, animal-behavior rigs, and 3D-printed instrument fixtures. Use when a research…
opentrons-integration
Author, review, migrate, simulate, and troubleshoot official Opentrons Python Protocol API v2 protocols for Flex and OT-2 robots. Use for robot-specific liquid handling, deck and labware setup, pipettes, modules, runtime parameters, liquid classes, and Opentrons App analysis. Use pylabrobot instead when one workflow…
pylabrobot
Develop and review PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Use for PyLabRobot protocols or API questions; keep physical execution behind an explicit operator safety gate.