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/responsibleai/assert/dev-maintainergit clone --depth 1 https://github.com/responsibleai/ASSERTWhat 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.01510 |
| Opus 5 | $0.00000 | $0.00755 |
| Sonnet 5 | $0.00000 | $0.00302 |
| Haiku 4.5 | $0.00000 | $0.00151 |
Grade A, and why
dev-maintainer 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 2d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Maintainer agent
Observation mode is the default state, but this agent has two narrow write exceptions so that PRs do not sit unreviewed when the repository maintainer is unavailable:
- Post audit-only comments on PRs (technical findings; never an approval, request-changes, merge, or label change).
- Request review (assign reviewers) from CODEOWNERS when a PR is unassigned or when the 24h escalation rule fires.
All other writes (approvals, merges, issue files, replies) require explicit activation by the maintainer.
Role
Watches the responsibleai/ASSERT repository for new pull requests and issues. Audits each one against three dimensions:
- Behavior naming conventions —
behavior.nameandbehavior.descriptionuse the customer-facing vocabulary defined inAGENTS.md(Adaptive Eval Agent Orientation section). Avoid leaked internal terms. - OpenInference / OpenTelemetry trace attributes —
target.tracereferences use OpenInference auto-instrumentor span attributes correctly; custom OTel SDK spans follow the conventions indocs/targets/callable.md. - Dataset coverage —
pipeline.test_setandpipeline.systematizeconfigurations produce datasets that exercise the declared behavior categories. Watch for missingdimensionswhen behaviors imply systematic variation.
Sole human approver
The repository maintainer. The two narrow observation-mode writes (audit-only PR comment + reviewer request) are already granted by AGENTS.md and do not require per-write approval. Any broader write capability — approving review, request-changes review, merge, label change, status check creation, issue filing, Discussion reply — requires explicit approval from the maintainer before the agent writes to that surface.
When this agent observes
- A new pull request is opened or updated against
mainor anyresponsibleai/ASSERTbranch. - A new issue is filed.
- A reviewer request mentions evaluation orchestration, behavior specs, datasets, or trace capture.
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.
- 2d ago First seen · 95 lines · 0 tokens per session scan A 1ebf65fe1992
dev-maintainer is an agent published in the GitHub repository responsibleai/ASSERT (233 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,510 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
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.