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 agentmods add agents/taketo-yoda/uv-sbom/devrelgit 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.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00520 |
| Opus 5 | $0.00000 | $0.00260 |
| Sonnet 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 today.
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.
- today First seen · 66 lines · 0 tokens per session scan A 8cf2fbecdc4c
devrel is an agent published in the GitHub repository Taketo-Yoda/uv-sbom (5 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
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
fsl-vacuity-reviewer
Use PROACTIVELY after adding or changing a .fsl spec under specs/ or examples/. Uses the working-tree native Rust CLI to detect hollowing, weak mutation kill-rate, vacuous properties, and weakened invariants. Read-only on specs; may run verifier commands.
python-pytest-architect
Creates, reviews, and modernizes Python 3.11+ test suites using pytest. Expert in pytest-mock (not unittest.mock), hypothesis property-based testing, pytest-asyncio, and pytest-bdd. Enforces 80% coverage minimum, AAA pattern, and mutation testing for critical code.