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/webmaxru/ai-native-dev/ard-registry-buildernpx skills add webmaxru/ai-native-dev --skill ard-registry-buildergit clone --depth 1 https://github.com/webmaxru/ai-native-devWrote 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/webmaxru/ai-native-dev/ard-registry-builder)<a href="https://agentmods.dev/skills/webmaxru/ai-native-dev/ard-registry-builder"><img src="https://agentmods.dev/badge/skills/webmaxru/ai-native-dev/ard-registry-builder.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.00180 | $0.02068 |
| Opus 5 | $0.00090 | $0.01034 |
| Sonnet 5 | $0.00036 | $0.00414 |
| Haiku 4.5 | $0.00018 | $0.00207 |
Grade A, and why
ard-registry-builder 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 3d 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.
3. For exploratory calls, hit endpoints directly with `curl` (see `references/registry-api.md`). 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 ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/ai-catalog.schema.json 8.0 KB
- assets/templates/enterprise.json 1.8 KB
- assets/templates/local-dev.json 515 B
- assets/templates/minimal.json 581 B
- evals/evals.json 4.7 KB
- evals/files/broken-catalog.json 801 B
- references/data-model.md 6.1 KB
- references/publishing.md 2.9 KB
- references/registry-api.md 5.8 KB
- references/validation-rules.md 3.7 KB
- scripts/new_catalog.py 2.4 KB runs code
- scripts/test_registry.py 10 KB runs code
- scripts/validate_catalog.py 16 KB runs code
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.
- 3d ago First seen · 128 lines · 180 tokens per session scan A d50ef6e32c1b
ard-registry-builder is a skill published in the GitHub repository webmaxru/ai-native-dev (1 stars, last pushed 3d ago), with no licence file. It adds 180 tokens to every session and 2,068 once invoked, about $0.0009 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-31.
Other skills, from other repositories
hyperbrief
Use AFTER hyperbrief-trigger-check returns FULLHYPERBRIEF, SUMMARYBRIEF, DEEPBRIEF, or MINIMALBRIEF. v0.9 adds the request tier (Hyperbrief.md §2.6) — a bare request for a brief is a SUMMARYBRIEF rather than the heaviest tier, and DEEPBRIEF (§0.6) is request-only and the only tier permitted to fan out, so an unnamed…
ultrasafe-crypto-reviewer
Pre-release simulated penetration testing from the cryptography attacker perspective — key management / random source / TLS misuse / signature scheme / constant-time violation / PQC readiness / cryptographic agility envelope. Triggered by Ultrasafe orchestrator (ultrasaferunfanout MCP tool) when the axis-set includes…
ultrasafe-methodology-compliance
Use BEFORE a publish-equivalent release (npm publish / pip upload / git push --tags to public) — Ultrasafe 8-agent fan-out 의 Methodology / Compliance attacker 시각. Test methodology gap · coverage cliff · compliance catalog (NIST 800-115 / OSSTMM / OWASP WSTG / PTES / ISO 27001:2022 / CIS v8.1) 의 16-cell 2D dispatch…
ultrasafe-supply-chain-auditor
Pre-release simulated penetration testing from the dependency / SBOM / typosquatting / signing-chain perspective. Invoke as Agent 3 of the Ultrasafe 8-agent fan-out (Ultrasafe.md §15.3) whenever the iteration axis-set includes usf-supply-chain, or whenever a release candidate touches dependency manifests (package.json…
ultrasafe-synthesizer
Pre-release security testing — retire-barrier fan-out sink. Aggregate the 7 attacker agents' findings (ai-llm / web-api / supply-chain / crypto / social-eng / methodology / threat-model) via BFT quorum 2f+1 cross-axis confirmation, diversity-enforced source independence (perspective × prompttemplatehash × seed 3-tuple…
ultrasafe-threat-model-lifecycle
Pre-release simulated penetration testing from the threat modeling (STRIDE/PASTA) + incident lifecycle + disclosure timing attacker perspective. Invoke as one of 8 attackers in Ultrasafe fan-out runtime when a publish-equivalent action (npm publish / pip upload / git push --tags to public / release-gate trigger) is…