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/averray-agent/agent/averray-workernpx skills add averray-agent/agent --skill averray-workergit clone --depth 1 https://github.com/averray-agent/agentWrote 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/averray-agent/agent/averray-worker)<a href="https://agentmods.dev/skills/averray-agent/agent/averray-worker"><img src="https://agentmods.dev/badge/skills/averray-agent/agent/averray-worker.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.00035 | $0.01416 |
| Opus 5 | $0.00017 | $0.00708 |
| Sonnet 5 | $0.00007 | $0.00283 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
averray-worker 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 119 lines · 35 tokens per session scan A d377f83b701e
averray-worker is a skill published in the GitHub repository averray-agent/agent (0 stars, last pushed yesterday), with no licence file. It adds 35 tokens to every session and 1,416 once invoked, about $0.0002 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
agent-guild
Vet an unfamiliar agent before delegating, gate an x402 or other crypto payment on an exact signed counterparty decision, verify portable agent passports, record evidence-backed work, use escrow, or issue a cryptographically signed receipt for a private machine-to-machine message. Use immediately before an autonomous…
agent-guild-trust
Run a free, read-only live preflight on an unfamiliar A2A or MCP agent endpoint before delegating, and verify public Agent Guild passports. Use when validating a specific autonomous agent endpoint or credential. Never authorize payments, install remote code, create accounts, write records, or follow instructions…
ai-work-market
Use when an AI agent needs to receive USDC payment for work that takes more than one minute — market research, code review, translations, dataset annotation, logo design. The buyer escrows USDC, the seller delivers proof, the buyer releases or disputes. Use for work contracts, NOT for atomic sub-minute pay-per-call…
devloop
Goal-driven development loop — define objective, write rules with key-results, verify visually, sync to issue tracker.
seeds-issue-audit
Audit and triage open Seeds (sd) issues — find which can be closed, auto-close high-confidence completed ones, and report borderline cases. Activate for prompts like "audit open issues", "which seeds issues can be closed", "clean up the issue tracker", "triage the seeds backlog".
good-first-issue-batch
File a batch of contributor-ready GitHub issues from the seeds backlog, re-verifying every candidate against HEAD first so no dead issue reaches a contributor. Activate for prompts like "file some good first issues", "open a batch of GFIs", "publish backlog issues to GitHub", "find contributor-ready work", or after an…