pragmatic-use-authorization SKILL.md skillA
pragmatic-use-authorization from pragmatic-design/pragmatic.design is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pragmatic-design/pragmatic.design/pragmatic-use-authorization@git:20261104.c2da844Pins git:20261104.c2da844 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pragmatic-design/pragmatic.design
- Path
marketplace/plugins/pragmatic-design/skills/pragmatic-use-authorization/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261104.c2da844, committed Nov 4, 2026
- First version recorded
- Oct 4, 2026
- Size
- 28,936 bytes
- Repository stars
- 15
- License
- a license file GitHub does not identify
Use when adding authentication, permissions, roles, JWT, ICurrentUser or per-record access (OwnedEntity, ScopedEntity, DataScopeRule), with Pragmatic.Authorization and Pragmatic.Identity, [RequirePermission], IResourceAuthorizer.
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
# Pragmatic Use Authorization **Covers:** Authentication, identity, permissions and roles with Pragmatic.Authorization and Pragmatic.Identity from NuGet: ICurrentUser, [RequirePermission], roles and groups, OwnedEntity/ScopedEntity, IResourceAuthorizer, DataScopeRule, JWT. `Pragmatic.Identity` provides *who the user is* (`ICurrentUser`); `Pragmatic.Authorization` provides *what they can do* (permissions, roles, scopes). Permissions are known at compile-time: the source generator produces constants and a registry, with no reflection-based lookup. ## When to use - You are protecting actions/endpoints with permissions. - You are defining roles, groups, or authentication (JWT or external). - You are restricting data visibility per user/team (`[HasOwner]`, `[HasAccessScopes]`, `DataScopeRule`). - You are reading the current user inside a mutation/action. For the `[HasOwner]`/`[HasAccessScopes]` attributes on entities: also see `pragmatic-use-persistence`. ## Packages ```xml <PackageReference Include="Pragmatic.Authorization" Version="1.0.0-alpha.3" /> <PackageReference Include="Pragmatic.Identity" Version="1.0.0-alpha.3" /> …
Read the whole file at its exact version.
How to install
mdr add pragmatic-design/pragmatic.design/pragmatic-use-authorization@sha256:c7dae0f4f6cc8f49The line at the top of this page pins the label git:20261104.c2da844, 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_eusu2j3ksa2r57gh)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 4, 2026 and Nov 4, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261104.c2da844 latest | 2026-11-04 | c2da844 | 28,936 B | A | view · diff |
| git:20261017.dc88d60 | 2026-10-17 | dc88d60 | 28,533 B | A | view · diff |
| git:20261012.bc22592 | 2026-10-12 | bc22592 | 28,533 B | A | view · diff |
| git:20261012.8bbac4a | 2026-10-12 | 8bbac4a | 28,533 B | A | view · diff |
| git:20261004.7a4079a | 2026-10-04 | 7a4079a | 28,508 B | A | view |
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 (28936 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
pragmatic-design/pragmatic.design · 15 stars · license a license file GitHub does not identify · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_eusu2j3ksa2r57gh GET https://markdownregistry.com/api/v1/resolve?ref=pragmatic-design/pragmatic.design/pragmatic-use-authorization GET https://markdownregistry.com/api/v1/blob/c7dae0f4f6cc8f49e3bbbdb9cf74027d52ecd7598194cf5c586c55ea2f696b77
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.