authentication skillA
authentication is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Establish who the caller is — session cookies, bearer tokens, refresh, and OAuth/OIDC flows — and put each where it belongs. Use when adding or changing login, logout, signup, session handling, token issuance or refresh, an identity-provider integration, or when a request arrives with a credential nobody validates. Not for deciding what an authenticated caller may then do (that is authorization), not for the login screen's design, and not for hand-rolling crypto..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Authentication Authentication answers one question: **who is making this request?** Every answer it produces is an input to authorization, never a substitute for it. A skill that conflates the two produces an app where being logged in is the only permission that exists. ## When this fires A credential is issued, accepted, refreshed or revoked. Adding login, wiring an identity provider, introducing an API key or token, changing session lifetime or cookie flags. It does not fire for "this user should not see that" — that is authorization. ## Procedure 1. **Find the mechanism that already exists before adding one.** Grep for session middleware, an auth library in the dependency manifest, existing cookie names, a provider SDK, `Authorization` header handling. Most "add auth" tasks are "extend auth". Two parallel auth systems is how a bypass gets built. 2. **Name the client type, in writing, before any code.** First-party browser app → server session with a cookie. Third-party, native or mobile client → bearer token. Service to service → client-credentials token or mutual TLS. This choice determines everything below; making it …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/authentication@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/authentication@sha256:0f7bf7e789cecff1Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_gh5owdrk72kpxeg5)
1 badge views in 30 days
Versions
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 (7116 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
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gh5owdrk72kpxeg5 GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/authentication GET https://markdownregistry.com/api/v1/blob/0f7bf7e789cecff11787b50c4e274624002b2e34002c684d95511741eb5bf197
Your agent 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.
More from nahid-sparktales/agent-dispatcher
Every file in nahid-sparktales/agent-dispatcher