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 UnboundCompute/security-agent-skills --skill hunting-adcs-certificate-template-abusegit clone --depth 1 https://github.com/UnboundCompute/security-agent-skillsWrote 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/unboundcompute/security-agent-skills/hunting-adcs-certificate-template-abuse)<a href="https://agentmods.dev/skills/unboundcompute/security-agent-skills/hunting-adcs-certificate-template-abuse"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/hunting-adcs-certificate-template-abuse/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/unboundcompute/security-agent-skills/hunting-adcs-certificate-template-abuse"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/hunting-adcs-certificate-template-abuse.svg" alt="Reviewed on agentmods" width="80" 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.00158 | $0.02034 |
| Opus 5.5 | $0.00063 | $0.00814 |
| Sonnet 5.5 | $0.00032 | $0.00407 |
| Haiku 4.5 | $0.00016 | $0.00203 |
Grade A, and why
hunting-adcs-certificate-template-abuse 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 1mo 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hunting ADCS certificate template abuse: when a standard user enrolls as a domain admin
A certificate authority in a Windows domain issues certificates that clients then use to authenticate, and the identity a certificate carries is whatever the authority put in it. That is safe only when the authority decides the identity from the authenticated enrollee, never from what the enrollee asked for. A template that lets the requester supply the subject alternative name, combined with a use that permits client authentication and enrollment rights granted to ordinary users, lets a standard user request a certificate naming a domain administrator and then authenticate as that administrator. Other template settings weaken the same boundary: a flag that carries the requester's identity into the issued certificate, or enrollment permissions loose enough that any user obtains a template meant for privileged roles. The bug is a certificate whose identity the low-privileged enrollee, not the authority, decided. You hunt these by reading each template's enrollment rights, subject source, and permitted uses.
When to use
- A certificate authority issues templates usable for domain authentication and standard users may enroll.
- A template lets the enrollee supply the subject or a subject alternative name rather than deriving it.
- Enrollment permissions or template flags may let an ordinary user obtain a privileged-identity certificate.
Scope check
Test certificate template abuse only in directories you own or are authorized to assess, on non-production or a lab domain, enrolling only for an identity you are permitted to test with and never authenticating as a real privileged principal outside the authorization. A confirmed abuse yields authentication as a privileged account, so keep every probe within scope. If you can't name the authorization, stop.
The loop
- Establish where the certificate's identity actually comes from first. For each template a standard user can enroll in, determine whether the authority derives the subject and any alternative name from the authenticated enrollee, or whether the enrollee supplies them, and whether the resulting certificate permits client authentication. This is the false-positive killer: a template that fixes the identity from the enrollee and forbids requester-supplied names cannot mint a privileged identity, however broad its enrollment rights. Name the identity source before crafting a request.
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.
- 1mo ago First seen · 141 lines · 158 tokens per session scan A 629dc6da066d
hunting-adcs-certificate-template-abuse is a skill published in the GitHub repository UnboundCompute/security-agent-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 158 tokens to every session and 2,034 once invoked, about $0.0006 per session on Opus 5.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-09.
Other skills, from other repositories
prodcheck-review
Review this codebase against the prodcheck pre-production checklists — security, performance, scale, integrations, post-launch readiness and people. Use when asked to check whether a project is ready to ship, to audit an area before launch, or to work through a specific checklist. Produces evidence with file:line…
integrate-arcjet-guard-genkit
Integrate Arcjet security into a Genkit JS agent using @arcjet/guard — wrap ai.defineTool, put guardMiddleware on generate({ use }) for unwrapped / MCP / filesystem tools, and read a caller-owned id from generate({ context }). Use when asked to add Arcjet to genkit, rate limit its tools, screen inbound messages, or…
integrate-arcjet-guard-tanstack-ai
Integrate Arcjet security into a TanStack AI chat() app using @arcjet/guard — put guardMiddleware first on chat({ middleware }) so onBeforeToolCall gates tools, and read a caller-owned id from chat({ context }). Use when asked to add Arcjet to TanStack AI, rate limit its tools, screen inbound messages, or block prompt…
integrate-arcjet-guard-claude-managed-agents
Integrate Arcjet security into Claude Managed Agents (hosted REST+SSE, beta managed-agents-2026-04-01) using @arcjet/guard — screen user.message / initialevents before sessions.events.send, and gate custom tools on agent.customtooluse. Use when asked to add Arcjet to Claude Managed Agents, rate limit custom tools, or…
linear-claude-skill
Manage Linear issues, projects, and teams.
varlock-claude-skill
Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits.