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 Asaiuta/reverse-workbench-skill --skill competition-lsass-ticket-materialgit clone --depth 1 https://github.com/Asaiuta/reverse-workbench-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/asaiuta/reverse-workbench-skill/competition-lsass-ticket-material)<a href="https://agentmods.dev/skills/asaiuta/reverse-workbench-skill/competition-lsass-ticket-material"><img src="https://agentmods.dev/badge/skills/asaiuta/reverse-workbench-skill/competition-lsass-ticket-material/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/asaiuta/reverse-workbench-skill/competition-lsass-ticket-material"><img src="https://agentmods.dev/badge/skills/asaiuta/reverse-workbench-skill/competition-lsass-ticket-material.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.00123 | $0.00737 |
| Opus 5 | $0.00062 | $0.00368 |
| Sonnet 5 | $0.00025 | $0.00147 |
| Haiku 4.5 | $0.00012 | $0.00074 |
Grade A, and why
competition-lsass-ticket-material 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 9d 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.
This is a copy
100% identical to competition-lsass-ticket-material — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competition LSASS Ticket Material
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 host artifact lives in LSASS, ticket caches, or adjacent credential material and the hard part is proving what is replayable.
Reply in Simplified Chinese unless the user explicitly requests English.
Quick Start
- Separate raw credential material from actually usable replay edges.
- Record logon session, LUID, ticket cache, package, account, and target service before broad conclusions.
- Keep host artifact, extracted secret, replay attempt, and resulting acceptance in one chain.
- Distinguish password, hash, ticket, DPAPI secret, SSP residue, and token by where each can actually be used.
- Reproduce the smallest host-artifact-to-accepted-privilege path that proves the decisive edge.
Workflow
1. Map LSASS And Adjacent Credential State
- Record logon sessions, LUIDs, ticket caches, package names, SSPs, DPAPI context, and any service-account material tied to the active path.
- Note whether the decisive value is a TGT, service ticket, delegated ticket, DPAPI secret, plaintext, hash, or package-specific secret.
- Keep host source, account context, and cache location tied together.
2. Prove Replay Or Acceptance
- Show where the extracted material is accepted: SMB, WinRM, service ticket use, DPAPI unwrap, Schannel, or another host or service edge.
- Record SPN, target host, logon session, ticket flags, encryption type, and resulting privilege or token change.
- Distinguish material that is present from material that is actually replayable in this path.
3. Reduce To The Decisive Credential Chain
- Compress the result to the smallest sequence: host artifact -> extracted material -> accepted replay or unwrap -> resulting capability.
- State clearly whether the decisive edge lives in LSASS memory, ticket cache reuse, DPAPI context, or accepting service behavior.
- If the task broadens into full host-to-host pivoting, hand back to the tighter Windows pivot skill.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 52 lines · 123 tokens per session scan A 32ef1100a9c8
competition-lsass-ticket-material is a skill published in the GitHub repository Asaiuta/reverse-workbench-skill (2 stars, last pushed 26d ago), licensed MIT. It adds 123 tokens to every session and 737 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to competition-lsass-ticket-material, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
osint-recon
A knowledge guide for open-source intelligence, or OSINT: collecting information from publicly available sources. It covers servers, websites, domains, and, when appropriate, people.
hackerone
A safety wrapper for HackerOne bug-bounty testing that reads a program's allowed targets and rules before handing each allowed asset to a penetration-testing workflow. HackerOne is a platform where companies invite researchers to report security bugs.
crypto-toolkit
A toolkit for encoding, decoding, hashing, and encrypting data in formats such as Base64, hexadecimal, URLs, JWTs, AES, RSA, and common ciphers.
redteam-cve-lookup
CVE lookup and applicability assessment domain card. Use after reconnaissance has identified products, versions, services, or fingerprints and red-team mode needs evidence-based CVE matching before deeper testing.
redteam-cve-validation
CVE validation domain card. Use after CVE lookup has produced applicable or candidate CVEs and red-team mode needs scoped evidence to decide whether to continue, pivot, or report.
secknowledge-skill
A knowledge base for testing the security of websites, software, and AI systems, including agents and language models.