lh-threat-modeling SKILL.md skillA
lh-threat-modeling from jrodrigopuca/local-agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jrodrigopuca/local-agents/lh-threat-modeling@v1.1Pins v1.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jrodrigopuca/local-agents
- Path
security/skills/lh-threat-modeling/SKILL.md- Versions recorded
- 1
- Latest version
- v1.1, committed Oct 14, 2026
- Size
- 4,956 bytes
- Repository stars
- 2
- License
- Apache-2.0
Mapping attack surface and trust boundaries before reading code: entry points, data flows, trust zones, and adversary goals. Trigger: load when starting a security assessment, designing a feature securely, or asked "what could an attacker do here / where are we exposed?".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## When to Use - Beginning a security review of a system or feature (do this BEFORE `lh-code-audit`) - Designing something new that handles auth, money, or sensitive data - "Where are we exposed?" / "What's our attack surface?" ## Critical Patterns ### 1. Enumerate the doors before checking any locks The first deliverable is the attack surface map, not a bug. List every way data or control ENTERS the system: public endpoints, authenticated endpoints, forms, file uploads, webhooks, message queues, URL params, headers, cookies, env, third-party callbacks, admin panels, CLI, and every dependency (their code runs as yours). An LLM in the system is a door too, and a strange one: anything the model reads (a document, a web page, a ticket, another user's message) is input from whoever wrote it, and anything the model can call (tools, queries, shell) is a sink that input can now aim at. The vulnerability you miss is almost always on a door that wasn't on anyone's diagram — the forgotten legacy endpoint, the internal API assumed private, the debug route left in. ### 2. Draw the trust boundaries — value lives at the crossings …
Read the whole file at its exact version.
How to install
mdr add jrodrigopuca/local-agents/lh-threat-modeling@sha256:2eeab686cc6004edThe line at the top of this page pins the label v1.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kev2ql5daioq2jk2)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 14, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4956 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jrodrigopuca/local-agents · 2 stars · license Apache-2.0 · pushed 2026-10-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kev2ql5daioq2jk2 GET https://markdownregistry.com/api/v1/resolve?ref=jrodrigopuca/local-agents/lh-threat-modeling GET https://markdownregistry.com/api/v1/blob/2eeab686cc6004ed9ef1e1d663d388307a1efe95e4a5f3316abbeca13a21def3
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.