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 agentmods add skills/ferroxlabs/wayland-core/parentnpx skills add FerroxLabs/wayland-core --skill parentgit clone --depth 1 https://github.com/FerroxLabs/wayland-coreWrote 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/ferroxlabs/wayland-core/parent)<a href="https://agentmods.dev/skills/ferroxlabs/wayland-core/parent"><img src="https://agentmods.dev/badge/skills/ferroxlabs/wayland-core/parent.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.00092 |
| Opus 5 | $0.00005 | $0.00046 |
| Sonnet 5 | $0.00002 | $0.00018 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
refactor-imports 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 yesterday.
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.
What it actually says
Refactor Imports
Preconditions
- A Rust file is open
- The file compiles
- Imports follow the std → external → internal pattern
Steps
- Read the file
- Identify the three import groups
- Sort each group alphabetically
- Group blank lines as needed
- Re-run cargo check
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.
- yesterday First seen · 20 lines · 10 tokens per session scan A 81ba376063b0
refactor-imports is a skill published in the GitHub repository FerroxLabs/wayland-core (39 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 92 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-09-04.
Other skills, from other repositories
stack-trace-rust-probe
Internal helper for meta-stack-trace-investigator. Use when a Rust panic or backtrace needs Rust-specific Result/Option checks, cargo test guidance, and patch targets.
rust-expert
Expert Rust programming assistant focused on idiomatic code, safety, and performance.
rust-expert
Rust programming expert for ownership, lifetimes, async/await, traits, and unsafe code.
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website"…
stack-trace-go-probe
Internal helper for meta-stack-trace-investigator. Use when a Go panic or stack trace needs Go-specific nil/error checks, go test reproducer guidance, and patch targets.