auditing-cross-account-role-trust-boundaries SKILL.md skillA
auditing-cross-account-role-trust-boundaries from unboundcompute/security-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add unboundcompute/security-agent-skills/auditing-cross-account-role-trust-boundaries@git:20260827.b5f41a4Pins git:20260827.b5f41a4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- unboundcompute/security-agent-skills
- Path
skills/auditing-cross-account-role-trust-boundaries/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260827.b5f41a4, committed Aug 27, 2026
- Size
- 9,356 bytes
- Repository stars
- 26
- License
- MIT
Audit cross-account IAM role assumption for trust policies that let the wrong principal assume a role: a trust policy with a wildcard or overbroad principal, a missing or unverifiable external ID on a third-party role, a confused-deputy path where a vendor assumes your role on any customer's behalf, and a role chain that reaches privileges the origin principal should never hold. Covers AWS assume-role trust policies, condition keys that should scope who may assume, and the transitive reach of…
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
# Auditing cross-account role trust boundaries: when the trust policy lets the wrong caller in A role's trust policy decides who may assume it, and in a multi-account or partner setup that policy is the whole boundary between organizations. It fails in quiet ways. A principal element written as a wildcard, or as an entire account rather than a specific role, lets any identity in that account assume the role. A third-party integration role that omits or does not verify an external ID is open to the confused-deputy attack, where the vendor is tricked into assuming your role on an attacker's behalf. And assumption chains, where one role assumes another, can carry a low-privilege origin into high-privilege territory the trust policies never meant to connect. You audit these by reading each trust policy for who it actually admits and by following where an admitted principal can go next. ## When to use - Roles in one account can be assumed from another account, a partner organization, or a third-party vendor. - A trust policy uses a broad principal, or a third-party role relies on an external ID for scoping. …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/auditing-cross-account-role-trust-boundaries@sha256:53c6392d7c6da1b6The line at the top of this page pins the label git:20260827.b5f41a4, 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_gh2j4fn2ksr45sek)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 27, 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 (9356 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
unboundcompute/security-agent-skills · 26 stars · license MIT · pushed 2026-09-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gh2j4fn2ksr45sek GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/auditing-cross-account-role-trust-boundaries GET https://markdownregistry.com/api/v1/blob/53c6392d7c6da1b617109240b02e6baba3b998c78aa53304e0a2f681d594e00d
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.