developer-trust-profile SKILL.md skillA
developer-trust-profile from tomzx/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tomzx/agents/developer-trust-profile@git:20261007.b35fc4bPins git:20261007.b35fc4b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tomzx/agents
- Path
skills/developer-trust-profile/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261007.b35fc4b, committed Oct 7, 2026
- First version recorded
- Apr 12, 2026
- Size
- 7,458 bytes
- Repository stars
- 12
- License
- MIT
Create, view, or update a developer trust profile for a GitHub user. Tracks trust level, strengths, weaknesses, PR patterns, and review history.
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
# Developer Trust Profile
Manages per-developer trust profiles that inform PR review behavior.
Each profile lives in its own file and accumulates observations across reviews.
Call this skill to view a profile, create one from scratch, or update it after a PR review.
## Prerequisites
- GitHub username (`$1`) of the developer
- Optional: `--after-review <owner/repo> <pr_number> <approved|not_approved>` to update after a review
## Profile Location
```
~/.developer-trust/{github_username}.md
```
## Trust Levels
| Level | Meaning | Effect on quick-pr-review |
|-------|---------|--------------------------|
| `trusted` | Developer consistently produces high-quality PRs | Standard checks, prefer approval on borderline cases |
| `neutral` | Unknown or mixed track record | Standard checks, default behavior |
| `cautious` | History of issues, missed edge cases, or unclear PRs | Apply stricter interpretation of checks, flag marginal cases |
| `always_reject` | Persistent quality/policy issues warranting manual review | Never auto-approve; always require human review |
## Workflow
```
Ensure ~/.developer-trust is a git repo
|
Read existing profile (or start fresh)
…Read the whole file at its exact version.
How to install
mdr add tomzx/agents/developer-trust-profile@sha256:6cf8d3a6d0c08f0dThe line at the top of this page pins the label git:20261007.b35fc4b, 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_omyo7vz664vamblp)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Apr 12, 2026 and Oct 7, 2026, about one every 59 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.b35fc4b latest | 2026-10-07 | b35fc4b | 7,458 B | A | view · diff |
| git:20261004.00bb0c5 | 2026-10-04 | 00bb0c5 | 7,458 B | A | view · diff |
| git:20260415.bb96811 | 2026-04-15 | bb96811 | 7,463 B | A | view · diff |
| git:20260412.3b98778 | 2026-04-12 | 3b98778 | 7,461 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 (7458 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
tomzx/agents · 12 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_omyo7vz664vamblp GET https://markdownregistry.com/api/v1/resolve?ref=tomzx/agents/developer-trust-profile GET https://markdownregistry.com/api/v1/blob/6cf8d3a6d0c08f0dfaad239c7c3f37dd5c33f63e11966a95000696da6eacaf47
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.