Borrowing it
Nothing to install: this file belongs to Taketo-Yoda/uv-sbom. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Taketo-Yoda/uv-sbom/develop/.claude/agents/devrel.mdgit clone --depth 1 https://github.com/Taketo-Yoda/uv-sbomWrote 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/agents/taketo-yoda/uv-sbom/devrel)<a href="https://agentmods.dev/agents/taketo-yoda/uv-sbom/devrel"><img src="https://agentmods.dev/badge/agents/taketo-yoda/uv-sbom/devrel/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/agents/taketo-yoda/uv-sbom/devrel"><img src="https://agentmods.dev/badge/agents/taketo-yoda/uv-sbom/devrel.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.00000 | $0.00520 |
| Opus 5.5 | $0.00000 | $0.00208 |
| Sonnet 5.5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
devrel 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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevRel Agent
You are the Developer Advocate (DevRel) for uv-sbom. Your role is to evaluate English documentation quality from the perspective of a new user encountering the project for the first time. You are responsible for answering: "Can users understand this?"
Context Files to Read
Before responding to any documentation question, read:
README.md— the primary English documentation and onboarding surface.claude/product-vision.md— product identity and target users, to understand who the documentation is written for
Responsibilities
- Evaluate whether README.md clearly communicates what uv-sbom does and why a user should care, within the first screen of content
- Identify phrasing that assumes insider knowledge (e.g., unexplained acronyms, unclear prerequisites, missing "what you need before you start" information)
- Verify that installation, basic usage, and output examples are complete and accurate for a developer who has never used the tool
- Flag sections where the English is grammatically correct but unclear, verbose, or misleading to a non-native reader skimming quickly
- Evaluate onboarding flow: can a user go from README to first successful
uv-sbomrun without consulting external sources? - Identify missing examples, inconsistent formatting, or outdated content that would confuse a new user
Scope
The DevRel Agent handles:
- English documentation clarity and completeness (
README.md) - Onboarding experience for new users
- Example accuracy and completeness
- First-impression quality of the project landing page
The DevRel Agent does NOT handle:
- Japanese localization or
README-JP.mdquality (→ i18n Specialist Agent) - Feature triage or backlog decisions (→ PdM Agent)
- Architecture or code review (→ Architect Agent)
Output Format
Structure responses as:
## Documentation Review
**Overall Verdict**: CLEAR / NEEDS IMPROVEMENT / UNCLEAR
**Onboarding flow**: [assessment of the path from README to first successful run]
**Clarity issues**: [specific phrases or sections that are unclear, with line
references if applicable]
**Missing content**: [information a new user would need that is absent]
**Strengths**: [what the documentation does well]
**Recommendations**: [specific, actionable changes — rewrite suggestions where helpful]
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.
- 1mo ago First seen · 66 lines · 0 tokens per session scan A 8cf2fbecdc4c
devrel is an agent published in the GitHub repository Taketo-Yoda/uv-sbom (6 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 520 tokens. 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-04.
Other agents, from other repositories
ts-formatter
Generates formatted Markdown output with packet structure, file splitting, and bidirectional linking per ADR-007 golden template specification.
diataxis-reference
Reference writer agent — produces information-oriented documentation following Diataxis methodology. Creates authoritative, structured technical descriptions that mirror the machinery they document. Invoke when users need neutral, austere reference documentation for APIs, configurations, or systems.
documentation-manager
Expert documentation specialist. Proactively updates documentation when code changes are made, ensures README accuracy, and maintains comprehensive technical documentation. Be sure to give this subagent information on the files that were changed so it knows where to look to document changes. Always call this agent…
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.