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/superdesigndev/treg/write-provider-skillnpx skills add superdesigndev/treg --skill write-provider-skillgit clone --depth 1 https://github.com/superdesigndev/tregWrote 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/superdesigndev/treg/write-provider-skill)<a href="https://agentmods.dev/skills/superdesigndev/treg/write-provider-skill"><img src="https://agentmods.dev/badge/skills/superdesigndev/treg/write-provider-skill.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.00073 | $0.01546 |
| Opus 5 | $0.00036 | $0.00773 |
| Sonnet 5 | $0.00015 | $0.00309 |
| Haiku 4.5 | $0.00007 | $0.00155 |
Grade A, and why
write-provider-skill scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Call through `/call/` rather than curl-with-a-token: that exercises binding injection, token The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 128 lines · 73 tokens per session scan A d2fb99f64592
write-provider-skill is a skill published in the GitHub repository superdesigndev/treg (1,111 stars, last pushed yesterday), with no licence file. It adds 73 tokens to every session and 1,546 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
secrets-gitleaks
Hardcoded secret detection and prevention in git repositories and codebases using Gitleaks. Identifies passwords, API keys, tokens, and credentials through regex-based pattern matching and entropy analysis. Use when: (1) Scanning repositories for exposed secrets and credentials, (2) Implementing pre-commit hooks to…
gpt-image-2-style-library
Choose GPT-Image2 / gpt-image-2 visual styles and industrial prompt templates from the awesome-gpt-image-2 style library. Use when an agent needs to create, rewrite, classify, or improve image-generation prompts with repository-backed templates, categories, style tags, scene tags, pitfalls, and example cases.
cis-aws-foundations-2.12
Ensure access keys are rotated every 90 days or less.
cis-aws-foundations-2.16
Ensure IAM instance roles are used for AWS resource access from instances.
cis-aws-compute-12.3
Ensure AWS Secrets manager is configured and being used by Lambda for databases.
cis-aws-compute-3.6
Ensure secrets are not passed as container environment variables in Amazon ECS task definitions.