Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add tomzx/agents --skill developer-trust-profilegit clone --depth 1 https://github.com/tomzx/agentsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tomzx/agents/developer-trust-profile)<a href="https://agentmods.dev/skills/tomzx/agents/developer-trust-profile"><img src="https://agentmods.dev/badge/skills/tomzx/agents/developer-trust-profile/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tomzx/agents/developer-trust-profile"><img src="https://agentmods.dev/badge/skills/tomzx/agents/developer-trust-profile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00036 | $0.01758 |
| Opus 5.5 | $0.00014 | $0.00703 |
| Sonnet 5.5 | $0.00007 | $0.00352 |
| Haiku 4.5 | $0.00004 | $0.00176 |
Grade A, and why
developer-trust-profile scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 22d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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)
|
Mode: view or update?
/ \
View Update
| |
Print profile Fetch PR metadata
|
Synthesize observations
(strengths, weaknesses,
patterns seen in diff)
|
Update profile sections
+ append review history row
|
Write profile file
|
git commit
Steps
1. Initialize repository
Ensure ~/.developer-trust exists and is a git repository:
mkdir -p ~/.developer-trust
git -C ~/.developer-trust init
git init is idempotent: safe to run even if the directory is already a repository.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 22d ago Changed · +8 lines 6cf8d3a6d0c0
- 24d ago Changed 2f2d6871a441
- 1mo ago First seen · 219 lines · 36 tokens per session scan A e64c3328d5d8
developer-trust-profile is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,758 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…