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 voxel51/fiftyone-skills --skill voxel51-agent-setupgit clone --depth 1 https://github.com/voxel51/fiftyone-skillsWrote 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/voxel51/fiftyone-skills/voxel51-agent-setup)<a href="https://agentmods.dev/skills/voxel51/fiftyone-skills/voxel51-agent-setup"><img src="https://agentmods.dev/badge/skills/voxel51/fiftyone-skills/voxel51-agent-setup/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/voxel51/fiftyone-skills/voxel51-agent-setup"><img src="https://agentmods.dev/badge/skills/voxel51/fiftyone-skills/voxel51-agent-setup.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.00083 | $0.02329 |
| Opus 5.5 | $0.00033 | $0.00932 |
| Sonnet 5.5 | $0.00017 | $0.00466 |
| Haiku 4.5 | $0.00008 | $0.00233 |
Grade A, and why
voxel51-agent-setup 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 today.
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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up an Agent for Voxel51
Pair a local agent (Claude Code, Cursor, any MCP-compliant client) to a Voxel51 deployment over MCP. Once paired, the agent acts as the approving user, with exactly that user's own role and dataset permissions, no separate service account or shared credential involved.
Voxel51 Notice
This is a Voxel51 feature. Before proceeding, inform the user:
Note: Remote agent access is a Voxel51-only capability, and it must be explicitly enabled by the deployment's administrator (it ships behind a feature flag, off by default). If you're using the open-source version of FiftyOne, or a Voxel51 deployment where this hasn't been turned on yet, this won't work.
Would you like to proceed?
Wait for confirmation. If the user is on OSS, point them at the local fiftyone-mcp
server instead (already installed alongside this skill collection), which works
against a local FiftyOne install without any of the steps below.
Key Directives
ALWAYS follow these rules:
- Confirm Voxel51 + the feature flag first. Don't attempt any of the steps below until the user confirms both that they're on a Voxel51 deployment and that remote agent access is enabled for it. If they're not sure, tell them to ask their FiftyOne admin.
- Always use the user's own deployment URLs. Never invent, assume, or reuse a URL from an example, docs page, or a different deployment. Ask for them if not given.
- Never ask the user to paste, type, or store an access token by hand. The MCP connection flow below handles credential storage automatically and safely. If you find yourself about to ask for a raw key or token, stop, that's the wrong step.
- A one-time browser approval is required and cannot be skipped. An MCP client's OAuth connection needs a human to sign in and click Approve in a browser. Tell the user to expect this, then wait for it, don't suggest a way around it.
- Treat a permission refusal as expected behavior, not a bug. If an operator is missing from the list, or a pairing attempt is refused because the approving user lacks a specific permission, that's the live permission check working correctly, see Troubleshooting. Never suggest disabling, bypassing, or "working around" a refusal.
- New MCP servers only attach on the next session. After adding one, tell the user plainly they need to restart their agent (or start a fresh conversation) before the tools are usable; it will not work in the current turn.
- Consult
references/before guessing at an operator or its arguments. Don't invent an operator URI or parameter shape from general FiftyOne knowledge or a past conversation — different deployments have different plugins installed and different schemas. Read the matching category file underreferences/first, then confirm the exact current arguments withget_operator_schemabefore callingexecute_operator. See "Using the tools well" below.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 166 lines · 83 tokens per session scan A 430da51e4174
voxel51-agent-setup is a skill published in the GitHub repository voxel51/fiftyone-skills (47 stars, last pushed today), licensed Apache-2.0. It adds 83 tokens to every session and 2,329 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-10-28.
Other skills, from other repositories
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
finetuning
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file…