oauth2-provider-design SKILL.md skillA
oauth2-provider-design from samber/developer-platform-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/developer-platform-skills/oauth2-provider-design@v1.0.4Pins v1.0.4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/developer-platform-skills
- Path
skills/oauth2-provider-design/SKILL.md- Versions recorded
- 7
- Latest version
- v1.0.4, committed Nov 1, 2026
- First version recorded
- Sep 1, 2026
- Size
- 23,136 bytes
- Repository stars
- 9
- License
- MIT
Design the OAuth2 authorization-server surface a B2B SaaS offers third-party apps - the OAuth 2.1 protocol baseline (PKCE for every client, no implicit or password grants, exact redirect matching), token TTL and refresh-rotation policy, scope taxonomy and granularity, consent-screen design with partial and incremental grants, client registration posture, and the tiered app-verification program. Use whenever the user mentions OAuth, "Sign in with X", access and refresh tokens, scopes, consent…
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
# OAuth2 Provider Design You are an OAuth provider designer. Design the authorization-server surface a platform offers third-party apps: protocol profile, token lifecycle, scope taxonomy, consent screen, registration, verification. Do it so a compromised app or leaked token is a contained event, and so the platform never faces the forced retrofit Salesforce's ISV ecosystem lived through in 2026. This is decision guidance for a platform/API team, not an RFC tutorial. The target profile is OAuth 2.1, with one precision to carry everywhere: - RFC 9700 (BCP 240, the OAuth Security Best Current Practice) is final and ratified (January 2025). - The consolidated OAuth 2.1 document (draft-ietf-oauth-v2-1) remains in draft. Check its current status before citing it as published. The requirements are settled convergence regardless of the document's own publication status. Never state that OAuth 2.1 itself is a published RFC without first confirming that's still accurate. …
Read the whole file at its exact version.
How to install
mdr add samber/developer-platform-skills/oauth2-provider-design@sha256:2aefead40f01fda3The line at the top of this page pins the label v1.0.4, 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_7mpaefojl5el3jbu)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Sep 1, 2026 and Nov 1, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.4 latest | 2026-11-01 | 26101ea | 23,136 B | A | view · diff |
| v1.0.3 | 2026-10-25 | 4e87402 | 22,919 B | A | view · diff |
| v1.0.2 | 2026-10-22 | 62f14ef | 22,882 B | A | view · diff |
| v1.0.2 | 2026-10-22 | be92436 | 22,870 B | A | view · diff |
| v1.0.1 | 2026-10-22 | fd3ebd6 | 22,870 B | A | view · diff |
| v1.0.1 | 2026-09-27 | 3f8efdb | 22,675 B | A | view · diff |
| v1.0.0 | 2026-09-01 | d45953a | 22,272 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 (23136 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
samber/developer-platform-skills · 9 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7mpaefojl5el3jbu GET https://markdownregistry.com/api/v1/resolve?ref=samber/developer-platform-skills/oauth2-provider-design GET https://markdownregistry.com/api/v1/blob/2aefead40f01fda3612c80c99fb81f6e80620e71cd3f10e06744b1e726c38eec
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.