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 CrestApps/CrestApps.AgentSkills --skill orchardcore-phone-number-verificationsgit clone --depth 1 https://github.com/CrestApps/CrestApps.AgentSkillsWrote 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/crestapps/crestapps.agentskills/orchardcore-phone-number-verifications)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-phone-number-verifications"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-phone-number-verifications/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/crestapps/crestapps.agentskills/orchardcore-phone-number-verifications"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-phone-number-verifications.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00126 | $0.02311 |
| Opus 5 | $0.00063 | $0.01156 |
| Sonnet 5 | $0.00025 | $0.00462 |
| Haiku 4.5 | $0.00013 | $0.00231 |
Grade A, and why
orchardcore-phone-number-verifications 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 8d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Phone Number Verifications - Prompt Templates
Verify Contact Phone Numbers
You are an Orchard Core expert. Generate accurate code, settings, recipes, and integration guidance for the CrestApps Phone Number Verifications module. It is a provider-agnostic framework that persists verification data on content items and supports later revalidation.
Guidelines
- Install
CrestApps.OrchardCore.PhoneNumbers.Verificationsin the web/startup project. - Enable a provider feature as well as the core verification feature; a provider feature enables the core feature through its dependency.
- The core feature depends on
OrchardCore.ContentsandCrestApps.OrchardCore.PhoneNumbers. - Attach
PhoneNumberVerificationPartonly to content types representing a contact or another verified number owner. - Use
IPhoneNumberVerificationManagerto select and invoke the configured provider. - Store results with
PhoneNumberVerificationPartExtensions, not a hand-written parallel data structure. - Do not equate a transport/provider failure with
Invalid; failures are retryable. - Use
IPhoneNumberVerificationProviderto add a provider and give it a stable provider key. - Add provider settings as a site display driver rather than application-wide static configuration.
- Let the built-in background task throttle and revalidate due records.
- Install external-provider packages and CrestApps packages in the web/startup project.
- All recipe JSON must be wrapped in
{ "steps": [...] }. - All C# classes must use the
sealedmodifier, except for View Models.
Features
| Feature | Feature ID | Purpose |
|---|---|---|
| Core | CrestApps.OrchardCore.PhoneNumbers.Verifications |
Parts, manager, settings, index, queue, report, and scheduled revalidation |
| AbstractAPI | CrestApps.OrchardCore.PhoneNumbers.Verifications.AbstractApi |
AbstractAPI Phone Validation provider |
| Veriphone | CrestApps.OrchardCore.PhoneNumbers.Verifications.Veriphone |
Veriphone provider |
| Twilio | CrestApps.OrchardCore.PhoneNumbers.Verifications.Twilio |
Twilio Lookup provider |
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.
- 8d ago First seen · 230 lines · 126 tokens per session scan A 6d988581d4e8
orchardcore-phone-number-verifications is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed 13d ago), licensed MIT. It adds 126 tokens to every session and 2,311 once invoked, about $0.0006 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-03.
Other skills, from other repositories
aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration, hosting, or deployment behavior; deciding…
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
clean-architecture-dotnet
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
csharp-expert
Expert-level C# development with .NET 8+, ASP.NET Core, LINQ, async/await, and enterprise patterns. Use when the user mentions C#, .NET, ASP.NET, enterprise, or Microsoft platforms, or when the task involves Modern C#, Async/Await, LINQ, or ASP.NET Core.
sfcc-job-development
Guide for developing custom jobs in Salesforce B2C Commerce Job Framework. Use this when asked to create batch jobs, scheduled tasks, chunk-oriented processing, or task-oriented jobs.
sfcc-hooks-registration
Register SFCC hooks via cartridge package.json and hooks.json. Use when adding hooks or troubleshooting hook registration.