auditing-serverless-event-source-trust SKILL.md skillA
auditing-serverless-event-source-trust 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-serverless-event-source-trust@git:20260821.4f2a732Pins git:20260821.4f2a732 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-serverless-event-source-trust/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260821.4f2a732, committed Aug 21, 2026
- Size
- 9,329 bytes
- Repository stars
- 26
- License
- MIT
Audit event-driven function handlers that trust the event because it arrived from inside the platform: a handler that treats any delivered event as authentic without verifying its true source or integrity, event fields flowing untrusted into a database write, command, downstream call, or constructed path, a function reachable by several event types or actors that runs privileged logic for one that should not trigger it, and an over-broad execution identity that turns a single spoofed or…
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 serverless event-source trust: when the handler trusts the event because it came from inside Event-driven functions invert the usual request model: instead of a caller reaching an endpoint, a platform delivers an event to a handler. The recurring mistake is treating that delivery as authentication, the handler assumes the event is genuine, well-formed, and authorized simply because it came through the platform's plumbing. But the event source may accept writes from more parties than intended, the payload is attacker-influenceable input, and the same handler may be reachable by triggers it should never honor. The event payload is the source, the handler's action is the sink, and the bug is trust that was assumed rather than verified. You find it by mapping each function to what can trigger it and asking what the handler checks before it acts. ## When to use - Functions are triggered by events from queues, object-store notifications, schedules, topics, or gateways. - A handler trusts the event payload's contents or its claimed source without verifying either. - Per-event-type authorization or source authentication is assumed rather than checked in the handler. …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/auditing-serverless-event-source-trust@sha256:1d53b699c51f4fe0The line at the top of this page pins the label git:20260821.4f2a732, 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_h26723cujknmdbnj)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 21, 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 (9329 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_h26723cujknmdbnj GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/auditing-serverless-event-source-trust GET https://markdownregistry.com/api/v1/blob/1d53b699c51f4fe0996993279d1359db63125fd4e4bbfa15c35733a71410279c
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.