How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

competition-ad-certificate-abuse - Skill

Name: competition-ad-certificate-abuse
Author: zhaoxuya520

Imported from zhaoxuya520/reverse-skill (CTF-Sandbox-Orchestrator/competition-ad-certificate-abuse/SKILL.md). Install upstream with npx skills add zhaoxuya520/reverse-skill --skill competition-ad-certificate-abuse. Copyright stays with the author.

Competition AD Certificate Abuse

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive identity edge is certificate-based and the hard part is proving how a template or CA policy turns into accepted privilege.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

Identify the CA, template, enrolling principal, and accepting service before diving into every certificate detail.
Separate template enrollability from cert-based authentication or privilege acceptance.
Record EKUs, subject or SAN controls, issuance requirements, enrollment rights, and mapping behavior in compact blocks.
Tie the issued cert to one accepted path: PKINIT, Schannel, LDAPS, WinRM, or another mapped service.
Reproduce the smallest certificate issuance-to-acceptance chain that yields the decisive privilege.

Workflow

1. Map CA And Template Trust

Record CA configuration, template name, enrollment permissions, manager approval, authorized signatures, EKUs, subject requirements, and SAN behavior.
Note whether the path depends on alternate subject names, UPN, DNS names, enrollment agent behavior, or template supersedence.
Keep principal, template, and issuance policy tied together.

2. Prove Cert-To-Privilege Acceptance

Show how the issued certificate is mapped or accepted: PKINIT, smartcard logon, Schannel auth, service mapping, or explicit certificate mapping.
Record serial, subject, SAN, EKU, validity, and the exact service or domain edge that accepts it.
Distinguish certificate issuance from the separate step where privilege is actually granted.

3. Reduce To The Decisive Abuse Chain

Compress the path to the smallest sequence: enrollment right or misconfig -> issued cert -> accepted mapping -> resulting privilege.
State clearly whether the weakness lives in template config, CA policy, mapping logic, relay path, or enrollment rights.
If the task is really about delegation or ticket transformation after PKINIT, switch back to the tighter Kerberos skill.

Read This Reference

Load references/ad-certificate-abuse.md for the AD CS checklist, template checklist, and evidence packaging.

What To Preserve

CA names, template names, rights, EKUs, issuance flags, SAN controls, and mapping details
Issued certificate fields, serials, subjects, SANs, and the accepting service or logon path
The smallest reproducible enrollment-to-privilege chain

Install competition-ad-certificate-abuse and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "zhaoxuya520-reverse-skill-competition-ad-certificate-abuse", "kind": "skill", "name": "competition-ad-certificate-abuse", "description": "Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for AD CS, certificate templates, enrollment rights, EKUs, SAN controls, PKINIT, certificate mapping, and cert-based privilege paths. Use when the user asks about ESC-style abuse, certificate templates, enrollment agents, EKUs, SAN or subject controls, smartcard or PKINIT logon, CA policy, or how an issued cert turns into accepted privilege. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.", "publisher": "zhaoxuya520", "version": "1.0.0", "capabilities": { "domains": [ "math" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for AD CS, certificate templates, enrollment rights, EKUs, SAN controls, PKINIT, certificate mapping, and cert-based privilege paths. Use when the user asks about ESC-style abuse, certificate templates, enrollment agents, EKUs, SAN or subject controls, smartcard or PKINIT logon, CA policy, or how an issued cert turns into accepted privilege. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/zhaoxuya520/reverse-skill", "path": "CTF-Sandbox-Orchestrator/competition-ad-certificate-abuse/SKILL.md", "ref": "HEAD", "url": "https://github.com/zhaoxuya520/reverse-skill/blob/HEAD/CTF-Sandbox-Orchestrator/competition-ad-certificate-abuse/SKILL.md", "key": "zhaoxuya520/reverse-skill/CTF-Sandbox-Orchestrator/competition-ad-certificate-abuse/SKILL.md" } }, "instructions": "# Competition AD Certificate Abuse\n\nUse this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.\n\nUse this skill when the decisive identity edge is certificate-based and the hard part is proving how a template or CA policy turns into accepted privilege.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Identify the CA, template, enrolling principal, and accepting service before diving into every certificate detail.\n2. Separate template enrollability from cert-based authentication or privilege acceptance.\n3. Record EKUs, subject or SAN controls, issuance requirements, enrollment rights, and mapping behavior in compact blocks.\n4. Tie the issued cert to one accepted path: PKINIT, Schannel, LDAPS, WinRM, or another mapped service.\n5. Reproduce the smallest certificate issuance-to-acceptance chain that yields the decisive privilege.\n\n## Workflow\n\n### 1. Map CA And Template Trust\n\n- Record CA configuration, template name, enrollment permissions, manager approval, authorized signatures, EKUs, subject requirements, and SAN behavior.\n- Note whether the path depends on alternate subject names, `UPN`, DNS names, enrollment agent behavior, or template supersedence.\n- Keep principal, template, and issuance policy tied together.\n\n### 2. Prove Cert-To-Privilege Acceptance\n\n- Show how the issued certificate is mapped or accepted: PKINIT, smartcard logon, Schannel auth, service mapping, or explicit certificate mapping.\n- Record serial, subject, SAN, EKU, validity, and the exact service or domain edge that accepts it.\n- Distinguish certificate issuance from the separate step where privilege is actually granted.\n\n### 3. Reduce To The Decisive Abuse Chain\n\n- Compress the path to the smallest sequence: enrollment right or misconfig -> issued cert -> accepted mapping -> resulting privilege.\n- State clearly whether the weakness lives in template config, CA policy, mapping logic, relay path, or enrollment rights.\n- If the task is really about delegation or ticket transformation after PKINIT, switch back to the tighter Kerberos skill.\n\n## Read This Reference\n\n- Load `references/ad-certificate-abuse.md` for the AD CS checklist, template checklist, and evidence packaging.\n\n## What To Preserve\n\n- CA names, template names, rights, EKUs, issuance flags, SAN controls, and mapping details\n- Issued certificate fields, serials, subjects, SANs, and the accepting service or logon path\n- The smallest reproducible enrollment-to-privilege chain", "cost": { "context_tokens": 673 } }

competition-ad-certificate-abuse

About

Competition AD Certificate Abuse

Quick Start

Workflow

1. Map CA And Template Trust

2. Prove Cert-To-Privilege Acceptance

3. Reduce To The Decisive Abuse Chain

Read This Reference

What To Preserve

Install competition-ad-certificate-abuse and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews