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/woohyun212/security-skill/cert-parsenpx skills add woohyun212/security-skill --skill cert-parsegit clone --depth 1 https://github.com/woohyun212/security-skillWrote 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/woohyun212/security-skill/cert-parse)<a href="https://agentmods.dev/skills/woohyun212/security-skill/cert-parse"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/cert-parse.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.00015 | $0.01949 |
| Opus 5 | $0.00008 | $0.00975 |
| Sonnet 5 | $0.00003 | $0.00390 |
| Haiku 4.5 | $0.00002 | $0.00195 |
Grade A, and why
cert-parse 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 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.
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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What this skill does
Accepts an X.509 certificate file or PEM text and uses openssl x509 to parse the Subject, Issuer, SAN, validity period, public key info, and extension fields. If a CA bundle is provided, performs chain verification with openssl verify, and automatically checks for common issues such as weak keys, expiry, and self-signing.
When to use
- Inspecting a server certificate before or after deployment
- Debugging certificate chain errors (e.g., UNABLE_TO_GET_ISSUER_CERT)
- Checking certificate-related vulnerabilities (weak keys, wildcard misuse, etc.) during bug bounty or penetration testing
Prerequisites
opensslinstalled (built into Linux/macOS)- Certificate file (PEM/DER) or PEM text
- CA bundle file for chain verification (optional)
Inputs
| Variable | Description | Example |
|---|---|---|
CERT_INPUT |
PEM file path or remote host | /path/to/cert.pem or example.com:443 |
CA_BUNDLE |
(optional) CA bundle file path | /etc/ssl/certs/ca-certificates.crt |
Workflow
Step 1: Extract PEM from certificate source
CERT_INPUT="/path/to/cert.pem" # or "example.com:443"
WORK_CERT="/tmp/target_cert.pem"
# Determine whether input is a file or host:port
if [ -f "$CERT_INPUT" ]; then
echo "=== Loading certificate from file: $CERT_INPUT ==="
# Auto-convert DER format to PEM
if openssl x509 -in "$CERT_INPUT" -noout 2>/dev/null; then
cp "$CERT_INPUT" "$WORK_CERT"
echo "PEM format confirmed"
else
openssl x509 -in "$CERT_INPUT" -inform DER -out "$WORK_CERT" 2>/dev/null && \
echo "DER -> PEM conversion complete" || echo "Certificate format parsing failed"
fi
else
echo "=== Fetching certificate from remote host: $CERT_INPUT ==="
HOST=$(echo "$CERT_INPUT" | cut -d: -f1)
PORT=$(echo "$CERT_INPUT" | cut -d: -f2)
PORT=${PORT:-443}
echo | openssl s_client \
-connect "${HOST}:${PORT}" \
-servername "$HOST" \
2>/dev/null | openssl x509 -out "$WORK_CERT"
echo "Remote certificate saved: $WORK_CERT"
fi
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 · 201 lines · 15 tokens per session scan A 6fd890af2850
cert-parse is a skill published in the GitHub repository woohyun212/security-skill (21 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 1,949 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…