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 wangyendt/wayne-skills --skill stereo-tag-matchergit clone --depth 1 https://github.com/wangyendt/wayne-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/wangyendt/wayne-skills/stereo-tag-matcher)<a href="https://agentmods.dev/skills/wangyendt/wayne-skills/stereo-tag-matcher"><img src="https://agentmods.dev/badge/skills/wangyendt/wayne-skills/stereo-tag-matcher/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/wangyendt/wayne-skills/stereo-tag-matcher"><img src="https://agentmods.dev/badge/skills/wangyendt/wayne-skills/stereo-tag-matcher.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.00074 | $0.00729 |
| Opus 5 | $0.00037 | $0.00365 |
| Sonnet 5 | $0.00015 | $0.00146 |
| Haiku 4.5 | $0.00007 | $0.00073 |
Grade A, and why
pywayne-cv-stereo-tag-matcher 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 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.
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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pywayne Stereo Tag Matcher
This module matches AprilTags detected in stereo camera pairs.
Quick Start
from pywayne.cv.stereo_tag_matcher import StereoTagMatcher
from pathlib import Path
# Initialize matcher with custom colors
matcher = StereoTagMatcher(
target_height=600,
line_color=(0, 0, 255), # Red
all_tag_color=(0, 255, 0), # Green
common_tag_color=(0, 255, 255) # Yellow
)
# Process stereo pair
left_img = Path('left.png')
right_img = Path('right.png')
matched_info, stitched = matcher.process_pair(left_img, right_img, show=True)
# Save result
if stitched is not None:
import cv2
cv2.imwrite('stereo_result.png', stitched)
Initialization
matcher = StereoTagMatcher(
target_height=600, # Fixed height for resizing
line_color=(0, 0, 255), # Custom line color (BGR)
line_thickness=2,
box_thickness=2,
all_tag_color=(0, 255, 0),
common_tag_color=(0, 255, 255)
)
Input
| Parameter | Type | Description |
|---|---|---|
image1_input |
str, Path, or np.ndarray | Left camera image |
image2_input |
str, Path, or np.ndarray | Right camera image |
show |
bool | Display stitched result with cv2.imshow |
Output
Returned Dictionary
{
"tag_id": {
"cam1_center": (x, y), # Left image center
"cam1_corners": [(x1, y1), ...], # Left image corners
"cam2_center": (x, y), # Right image center
"cam2_corners": [(x1, y1), ...] # Right image corners
},
...
}
Only tags found in both images are included in the output.
Visualization
The stitched image displays:
- All tags - Green boxes (BGR: 0, 255, 0)
- Common tags - Yellow boxes (BGR: 0, 255, 255)
- Connection lines - Red lines connecting common tag centers (BGR: 0, 0, 255)
Use Cases
- Stereo camera calibration - Match common tags to calibrate stereo cameras
- Robot vision - Identify shared landmarks for navigation
- Augmented reality - Track common fiducial markers
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 · 99 lines · 74 tokens per session scan A e875dbfb294e
pywayne-cv-stereo-tag-matcher is a skill published in the GitHub repository wangyendt/wayne-skills (8 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 729 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-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.