security-architecture-review SKILL.md skillA
security-architecture-review from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/security-architecture-review@git:20260916.0e7cd01Pins git:20260916.0e7cd01 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/security/skills/security-architecture-review/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260916.0e7cd01, committed Sep 16, 2026
- First version recorded
- Aug 29, 2026
- Size
- 4,386 bytes
- Repository stars
- 2,543
- License
- MIT
Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a third-party integration, or decide whether a design is safe to build.
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
# Security architecture review ## Review in this order Attention spent in this order finds the most consequential problems first. **1. Authentication.** How identity is established, how sessions are represented, how they expire, what happens on password reset and account recovery. Recovery flows are the most commonly weakest path into an account and the least reviewed. **2. Authorization.** The one that matters most and gets least attention. For every endpoint and every object: who is allowed, and where is that checked? The characteristic failure is checking on the way in but not on the object itself, so any authenticated user can reach any record by changing an identifier. Check multi-tenant isolation explicitly and by test, not by reading. Assume every identifier in a request is attacker-controlled, because it is. **3. Data.** What is collected, where it goes, where it rests, and who can read it. Sensitive data in logs, in error responses, in analytics payloads, and in client bundles — all four are routine findings. **4. Input and output.** Untrusted input reaching a query, a template, a command, a deserializer, or …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/security-architecture-review@sha256:4255c858b5f9c5ffThe line at the top of this page pins the label git:20260916.0e7cd01, 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_m545oyi7klupe34d)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 29, 2026 and Sep 16, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.0e7cd01 latest | 2026-09-16 | 0e7cd01 | 4,386 B | A | view · diff |
| git:20260901.0757404 | 2026-09-01 | 0757404 | 4,047 B | A | view · diff |
| git:20260901.aa45383 | 2026-09-01 | aa45383 | 3,818 B | A | view · diff |
| git:20260829.4c1a9d2 | 2026-08-29 | 4c1a9d2 | 3,497 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 (4386 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
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_m545oyi7klupe34d GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/security-architecture-review GET https://markdownregistry.com/api/v1/blob/4255c858b5f9c5ff47c03a1e21c3b7d05880b3dc8a86ebc66d53f512545e4def
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.