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 hamzabellouch/agent-skills --skill yolo-object-detectiongit clone --depth 1 https://github.com/hamzabellouch/agent-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/hamzabellouch/agent-skills/yolo-object-detection)<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/yolo-object-detection"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/yolo-object-detection/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/hamzabellouch/agent-skills/yolo-object-detection"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/yolo-object-detection.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.00087 | $0.01742 |
| Opus 5 | $0.00044 | $0.00871 |
| Sonnet 5 | $0.00017 | $0.00348 |
| Haiku 4.5 | $0.00009 | $0.00174 |
Grade A, and why
yolo-object-detection 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 8d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YOLO Object Detection & Tracking
End-to-end production pipelines for custom training, TensorRT quantization, multi-object tracking (ByteTrack), and real-time inference serving with YOLO.
1. Pipeline Architecture
+---------------------+ +------------------------------+ +---------------------------+
| Custom Dataset | ---> | YOLO Model Training | ---> | Export to TensorRT |
| (Roboflow / COCO) | | (PyTorch / Ultralytics) | | (FP16 / INT8 Calibration) |
+---------------------+ +------------------------------+ +---------------------------+
|
v
+---------------------+ +------------------------------+ +---------------------------+
| Stream Output | <--- | Real-Time Multi-Object | <--- | TensorRT Engine |
| (Bounding Boxes/IDs)| | Tracking (ByteTrack / BoT) | | High-Throughput Inference |
+---------------------+ +------------------------------+ +---------------------------+
2. Custom Dataset Definition & Model Training (train_yolo.py)
Dataset YAML Config (dataset.yaml)
path: /data/datasets/manufacturing_defects
train: images/train
val: images/val
test: images/test
names:
0: scratch
1: dent
2: crack
PyTorch Training Pipeline (train_yolo.py)
from ultralytics import YOLO
import torch
import logging
logging.basicConfig(level=logging.INFO)
logger = logging.getLogger(__name__)
def train_custom_yolo():
device = "cuda:0" if torch.cuda.is_available() else "cpu"
logger.info(f"Using device: {device}")
# Load baseline pre-trained YOLO model (e.g. YOLOv8x or YOLO11x)
model = YOLO("yolov8x.pt")
# Execute Distributed Training
results = model.train(
data="dataset.yaml",
epochs=100,
imgsz=640,
batch=32,
device=device,
workers=8,
optimizer="AdamW",
lr0=0.001,
weight_decay=0.0005,
val=True,
save=True,
project="yolo_defects_project",
name="experiment_v1"
)
# Validate trained model
metrics = model.val()
logger.info(f"mAP50-95: {metrics.box.map}")
logger.info(f"mAP50: {metrics.box.map50}")
if __name__ == "__main__":
train_custom_yolo()
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.
- 8d ago First seen · 229 lines · 87 tokens per session scan A 124acb638cf3
yolo-object-detection is a skill published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 1,742 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
prompt-engineering
Universal prompt engineering techniques for any LLM. Use when crafting, optimizing, or reviewing prompts for AI models. Triggers on requests like "improve this prompt", "write a system prompt", "optimize my instructions", "help me prompt engineer", "audit this prompt", "review my prompt", or when building agentic…
fixing-prompt
Prompt: Prompt Refinement and Optimization.
feature-engineering
When building training datasets, designing feature pipelines, or debugging training-serving skew.
streaming-patterns
When designing Kafka consumers/producers or implementing real-time pipelines.
inference-serving
When deploying a model to an API endpoint or optimizing inference latency.
model-evaluation
When evaluating a trained model, comparing versions, or performing fairness analysis.