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/vladkesler/initrunner/ssl-certificatenpx skills add vladkesler/initrunner --skill ssl-certificategit clone --depth 1 https://github.com/vladkesler/initrunnerWrote 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/vladkesler/initrunner/ssl-certificate)<a href="https://agentmods.dev/skills/vladkesler/initrunner/ssl-certificate"><img src="https://agentmods.dev/badge/skills/vladkesler/initrunner/ssl-certificate.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.1 | $0.00027 | $0.00452 |
| Opus 5 | $0.00014 | $0.00226 |
| Sonnet 5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
ssl-certificate 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 6d 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.
What it actually says
SSL/TLS certificate checking skill.
When to activate
- When the user asks about SSL or certificate status
- As a periodic deep check (check memory for last SSL check date -- run at most once per week per endpoint)
Check command
echo | openssl s_client -connect <host>:443 -servername <host> 2>/dev/null | openssl x509 -noout -dates -subject -issuer
Replace <host> with the hostname extracted from the endpoint URL
(strip the protocol and path).
Parsing output
The command returns:
notBefore=-- certificate start datenotAfter=-- certificate expiry datesubject=-- certificate subject (CN and/or SAN)issuer=-- certificate issuer (CA name)
Calculate days until expiry from the notAfter date using the current
timestamp from datetime.
Alert thresholds
| Days remaining | Severity |
|---|---|
| > 30 | No alert |
| 14-30 | Warning |
| 7-14 | Warning (urgent) |
| 1-7 | Critical |
| 0 or expired | Critical (emergency) |
Additional checks
- Subject match: Verify the CN or SAN matches the hostname being checked. Mismatches indicate a misconfigured certificate.
- Issuer: Check if the issuer is a recognized CA. Self-signed certificates in production are a finding.
MUST
- Include the exact expiry date and days remaining in the alert
- Include the hostname checked and the issuer name
- Store the SSL check result in semantic memory with category "ssl_check" to avoid redundant checks
MUST NOT
- Alert on self-signed certificates for staging/dev URLs (check if the URL contains "staging", "dev", "local", "localhost", "test")
- Run SSL checks more than once per week per endpoint (check memory first)
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.
- 6d ago First seen · 68 lines · 27 tokens per session scan A c714e61a8757
ssl-certificate is a skill published in the GitHub repository vladkesler/initrunner (41 stars, last pushed 5d ago), licensed Apache-2.0. It adds 27 tokens to every session and 452 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-08-30.
Other skills, from other repositories
Vizra ADK Tool Creation
Build custom tools for Vizra ADK agents - includes patterns for database, API, file, and email tools.
Vizra ADK Evaluation Framework
Test and evaluate AI agents with automated evaluations, assertions, and LLM-as-a-Judge patterns.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
Vizra ADK Agent Creation
Create AI agents with Vizra ADK - includes patterns for customer service, data analysis, and content generation agents.
Vizra ADK Workflows
Orchestrate complex multi-agent workflows - sequential, parallel, conditional, and loop patterns.
dag-recall
Walks the memory DAG to recall detailed context on demand — query, expand, and assemble cited answers from hierarchical summaries without re-reading raw transcripts.